What is the success of a software project?
The traditional idea of success is delivery on time, on budget and according to specification
Successful : completed on time , on budget, with all the features and functions as originally specified
Challenged : completed and operational but over budget, over the time estimate, with fewer features and functions than originally specified
Impaired : cancelled at some point during the development cycle
Without personal success, you’ll have trouble motivating yourself and employees.
Without technical success, your source code will eventually collapse under its own weight.
Without organizational success, your team may find that they’re no longer wanted in the company
organizational success : deliver value and decrease costs
(1) Agile projects release their most valuable features first and release new versions frequently, which dramatically increases value. When business needs change or when new information is discovered, agile teams change direction to match
(2) the best agile projects generate only a few bugs per month (review and refactor continually). They also eliminate waste by cancelling bad projects early and replacing expensive development practices with simpler ones
technical success : transparent, quick response, test-driven development
personal success :
#Executives and senior management
They will appreciate the team’s focus on providing a solid return on investment and the software’s longevity.
#Users, stakeholders, domain experts, and product managers
They will appreciate their ability to influence the direction of software development, the team’s focus on delivering useful and valuable software, and increased delivery frequency.
#Project and product managers
They will appreciate their ability to change direction as business needs change, the team’s ability to make and meet commitments, and improved stakeholder satisfaction.
They will appreciate their improved quality of life resulting from increased technical quality, greater influence over estimates and schedules, and team autonomy.
They will appreciate their integration as first-class members of the team, their ability to influence quality at all stages of the project, and more challenging, less repetitious work.