By Pekka Abrahamsson
Read or Download Agile Software Development Methods: Review and Analysis (VTT publications) PDF
Similar analysis books
Analysis of Reliability and Quality Control: Fracture Mechanics 1
This primary ebook of a 3-volume set on Fracture Mechanics is especially based at the titanic diversity of the legislation of statistical distributions encountered in quite a few medical and technical fields. those legislation are imperative in realizing the chance habit of parts and mechanical constructions which are exploited within the different volumes of this sequence, that are devoted to reliability and qc.
- Wavelets in Geophysics
- Cohort Analysis of Fertility in England and Wales, 1939-50
- Automated Face Analysis: Emerging Technologies and Research (Premier Reference Source)
- Design analysis of experiments
- Idempotent Analysis and Its Applications
Additional resources for Agile Software Development Methods: Review and Analysis (VTT publications)
Example text
Roles and responsibilities In this section, the roles of Crystal Clear and Crystal Orange are presented according to Cockburn (2002a). The basic difference between Crystal Clear and Orange is that in the former there is only one team in a project. In Crystal Orange there are multiple teams to follow though the project. In both methodologies, one job assignment may include multiple roles. In Crystal Clear the main roles requiring separate persons are (Cockburn 2002a): sponsor, senior designer-programmer, designer-programmer and user.
While doing so, he identifies and documents the roles and entities within the organization. A Business-Model Reviewer reviews all of the artifacts produced by the Business-Process Analyst and the Business Designer. ) for the end users of the system that is under development. A Toolsmith develops in-house tools to support development, to enhance automation for tedious, repeating tasks, and to improve the integration between tools. The number of people required in a RUP project varies considerably, depending on the scope in which the workflows are implemented.
Candidate architectures for the system are devised, and the schedule and cost are estimated for the entire project. In addition, estimates are made for the following elaboration phase. The elaboration phase is where the foundation of software architecture is laid. The problem domain is analyzed, bearing in mind the entire system that is being built. The project plan is defined in this phase – if the decision is made to proceed to the next phases at all. In order to be able to make that decision, RUP assumes that the elaboration phase will yield a sufficiently solid architecture along with sufficiently stable requirements and plans.