With more and more companies going global, geographicallydistributed teams, cultural difference, attrition, etc., add to the challenge. Team Software Process (TSP) is one of the ways to move towards becoming "better, faster and cheaper". This article gives details as to how TSP techniques can be followed to overcome some of the challenges of consistently delivering highquality product within the budget in the global model and plan the right thing, do the right thing and expect the right thing every time.
Delivering
the right software on schedule has long been one of the most difficult challenges
faced by many businesses. The rate of failure has been high, more than 60% of
medium and large software projects are "failures" in the sense that
they will be delayed by six months or more, and many will be cancelled.
Many
different responses to these problems have evolved in recent years, including
those discussed here and many others, such as CMMI, ISO 9000, TSP/PSP, and Six
Sigma. In response to these diverse approaches, many organizations find themselves
somewhat in a conflict and also confused as to what is best and what should come
first. The goal of this article is to offer some clarity as to how these different
approaches relate to one another, and to provide guidance on leveraging the best
of all these approaches.
Any
project can be defined in three dimensions. The first is the product definition
also called the "feature set". The second dimension is schedule "shipping
on time" and the third is "reliability". Different people have
different views about these dimensions. The QA team might think "reliability"
is the most important thing to do. The marketing team will talk about "feature
set" and the project leaders/management would think "shipping on time"
is very important. Thus, everybody ends up focusing on different priorities and
that may re+sult in a chaos which also impacts the shipping of the product.
|
