Artifact:
|
The Development-Organization Assessment describes the current status of the software organization in terms of current process, tools, peoples' competencies, peoples' attitudes, customers, competitors, technical trends, problems, and improvement areas. | |
Role: | Process Engineer |
Optionality/Occurrence: | Often produced outside the scope of a single project. |
Templates and Reports: | |
Examples: | |
UML Representation: | Not applicable. |
More Information: |
Input to Activities: | Output from Activities: |
The Development-Organization Assessment is used by the process engineer as a basis for configuring the process for a particular project.
The Development-Organization Assessment is also used to:
All though the Development-Organization Assessment is an essential input to activities performed to define a project's environment, it is often produced outside the scope of a single project, as part of the development organization's overall process engineering effort. We recommend that you adjust this to reflect the characteristics of your project organization as part of producing a tailored version of the development process. See Activity: Tailor the Process for the Project, Step: Analyze the project for further details.
A Process Engineer is responsible for the Development-Organization Assessment.
Completeness, format and formalism of artifact Development-Organization Assessment
will vary depending on factors like size and type of development, business context,
degree of novelty, to mention a few. For example, a large development organization
developing systems for Air Traffic Control will likely do a very thorough assessment
of the development organization to ensure that they meet certain requirements
imposed on the organization by a range of external stakeholders. Tailor the
Development-Organization Assessment to reflect the organization and development
effort.
Rational Unified Process |