#Hashtab psp series#
All of these phases are linear in nature and a series of metrics are recorded for each phase. All of these phases must be well documented as part of the process and followed strictly with checklists. TSP follows a Requirements document, design document, coding, test and deployment phased approach. There are no concepts of Test Driven Development or Emergent (simple) design. Within that 3 month iteration work proceeds strictly according to a waterfall system.
Oh, and recording in your workbook every step of the way.
#Hashtab psp software#
You might spend the majority of your time writing up design documents and cross referencing that design to your software requirements specification. Let's be clear - work doesn't mean programming. Everything is just considered work that must be done and from that you derive a Work Breakdown Structure. Priority of requirements are not considered or racked and stacked. Once a developer runs out of work, they can take over the load of other developers that may be falling behind. Each developer will get handed a stack of that work. There is a series of ceremonial meetings where requirements are drawn in blood and work is planned out. By this I mean that a stack of work is presented and agreed to up front with the customer. TSP was presented as a load-balanced type of 3 month iterative process. You can just imagine how awesome people's metrics started looking after they learned that management was reviewing them. It took about 2 months before management started asking the Team Leads for the individual metrics. The data is supposed to be protected so that it can't be used against individual developers by management. It was founded in academia and in my experience it struggles in the domain of business application development.ĭo you enjoy programming with a log book and a stop watch? That is how you measure your work. The development of TSP came about because organizations were struggling to meet the rigorous demands of CMMI. Its chief concern is making sure that a process is being captured, recorded, followed and measured.
The system itself is designed for repeatable process and nowhere does it advocate any value in the software that is being delivered. I could go on and on about the ensuing disaster that happened once this process began being forced upon a development staff of agilists who were actually producing high value software for the customer on a regular basis, but instead I'll talk about the TSP methodology. TSP was basically introduced and pitched to management by consultants as a means of helping to achieve the goal of CMMI level 3 certification.
0 kommentar(er)
