PBP in the TSP / PSP

The Team Software Process (TSP(sm)) and the Personal Software Process (PSP(sm)) from the Software Engineering Institute are two processes that are being used in many companies.  These have been written to help organisations improve their software development and project management processes and meet some of the Capability Maturity Model Goals and Practices.

The institutionalisation of these processes requires a very high degree of discipline within a project team.  This discipline and precision provides the real opportunities for improvement.

Underlying these processes are many of the concepts of Product Based Planning.  These are:

• A Launch Process to Initiate the project
• A series of development cycles to develop the project (ie like phases or stages)
• A development strategy that identifies a clear structure for the items to be produced:  Product, Component, Module, Part (like a Product Breakdown Structure)
• A set of cycles where functions are allocated to Cycles (sequencing the development of the functions, like a product flow diagram)).
• A set of specifications that clearly define the items that are produced.  This includes the process related items too.

ChangeAide is a comprehensive Product Based Planning tool that supports multiple project management models by altering the terminology to match the process. In general, the basic product based planning processes are the same; however, the terminology is different.

Question Answered?	YesPartiallyNo, Tell us why?Improvement!
Comments
Feedback	Reload Image

Revision: 3.1.14a

Customer Driven Solutions Limited©2007, 2008, 2009, 2010

Email: