<Project Name>
Development-Organization Assessment
Version <1.0>
[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).]
Revision History
|
Date |
Version |
Description |
Author |
|
<dd/mmm/yy> |
<x.x> |
<details> |
<name> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
1.3 Definitions, Acronyms and Abbreviations
4.4 Competencies, Skills and Attitudes
5.1 Size of Software-Development Effort
Development-Organization
Assessment
[The introduction of the Development-Organization Assessment should provide an overview of the entire document. It should include the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this Development-Organization Assessment.]
[Specify the purpose of this Development-Organization Assessment.]
[A brief description of the scope of this Development-Organization Assessment; what Project(s) it is associated with, and anything else that is affected or influenced by this document.]
[This subsection should provide the definitions of all terms, acronyms, and abbreviations required to properly interpret the Development-Organization Assessment. This information may be provided by reference to the project Glossary.]
[This subsection should provide a complete list of all documents referenced elsewhere in the Development-Organization Assessment. Each document should be identified by title, report number (if applicable), date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.]
[This subsection should describe what the rest of the Development-Organization Assessment contains and explain how the document is organized.]
[A brief description of the business domain in which the organization work.]
[A listing of the customers and what they expect of the products.]
[A listing of the competitors.]
[A listing of other stakeholders, such as suppliers and partners.]
[A brief description of the current development process. A list of problems.]
[A brief description of today's tool support.]
[A brief description of the internal organization, what roles and teams they have today.]
[An inventory of the competencies, skills and attitudes of the individuals in the organization.]
[A brief description of the "capacity for change".]
[A brief description of the size of the software.]
[A description of where product is on a scale between "green-field development" and maintenance.]
[A brief description of the type of application, and what that can mean for the development process.]
[A description of the technical complexity of the product.]
[List the major problem areas and opportunity areas, regardless of the categories to which they belong.]