s You are here: Home > Development > Implementation task: Develop and execute the SDP
UMP slogan Home | About UMP | FAQ | Discuss | Contacts | Site map
  Life cycle model   Development process   Support process   Organizational process   Product    
Implementation | Analysis | Architecture | Design | Programming & Testing | Integration | Qualification








Implementation tasks:

5.3.1.1 Adjust process
5.3.1.3 Choose methods & tools
5.3.1.4 Develop & execute SDP

 

 

References:

UMP glossary
Bibliography
Conventions & Notation

Task 5.3.1.4: Develop and execute the software development plan (SDP)

UMP
  Development Process

         Implementation Activity
<< previous task

 

Task goals To assure that the project process is optimized and adapted for both given target software product and the given development team.

The Software Development Plan (SDP) should describe project specifics, which are not covered by the chosen life cycle model and the Product Business Specification (PBS). In this sense the SDP should be developed as a supplement to the model and PBS.

The SDP should be based on the team knowledge, experience and culture to grant ease of following the SDP to each team member.

The SDP shall be developed and treated as an agreement by the team members.
Procedure
  1. Project Manager: Develops the SDP.
  2. Project Manager: Makes the SDP available to the project participants.
  3. Project Manager and Developers: Conduct Technical Review of the SDP. The goal is to have the SDP cleared with, and confirmed by, the developers.
  4. Project Manager: If necessary, agrees with the project participants, others than developers, on SDP.
  5. Project Manager: Publishes the corrected and approved SDP.
  6. Developers: Follow the SDP spirit, philosophy and directions.
  7. Participants: Propose changes.
Inputs Programming artifacts None
Model None
Documents
Checklists
Guides None
Outputs Programming artifacts None
Model None
Documents Software Development Plan (SDP)
Checklists None
Completion criteria The completion of the all the development tasks
Quality metrics

X = 1 - A/B

where A — # of the SDP topics, which are considered by the team members as adequate to attain the project and team goals, spirit, philosophy and ease of following;
B — the total # of the SDP topics.
To measure, conduct periodical (once every 1-2 weeks, depending on the iteration period) team members poll.
The closer X is to 100%, the better.

Milestones
  • 1st review and quality assessment, ASAP after the project start.
  • Intermediate review —depends on the iteration period, not less than 1.
  • Last review —after the release issue.
Task improvement opportunity events
  • Development problems (of any kind), which are considered by the team as the SDP application consequences
  • Team changes
  • Project scope changes

 

 

Last modified: 07-Jan-2005
Copyright © 2003—2005 Alexander Kozlinski. All rights reserved.
Use of this website signifies your agreement to the Terms of Use