Entries by 'Bill Nichols'

Addressing the Challenges of Agile with TSP: A Case Study

Agile , Team Software Process (TSP) 3 Comments »

By Bill Nichols,
Senior Member of the Technical Staff
Software Engineering Process Management

Bill NicholsThis post is the third and final installment in a three-part series that explains how Nedbank, one of the largest banks in South Africa, is rolling out the SEI’s Team Software Process (TSP) throughout its IT organization. In the first post of this series, I examined how Nedbank addressed issues of quality and productivity among its software engineering teams using TSP at the individual and team level. In the second post, I discussed how the SEI worked with Nedbank to address challenges with expanding and scaling the use of TSP at an organizational level. In this post, I first explore challenges common to many organizations seeking to improve performance and become more agile and conclude by demonstrating how SEI researchers addressed these challenges in the TSP rollout at Nedbank.

Read more...

Rolling Out TSP Organizational Performance Improvement: A Case Study

Team Software Process (TSP) No Comments »

Second Installment in a Three-Part Series
By Bill Nichols,
Senior Member of the Technical Staff
Software Engineering Process Management

Bill NicholsThis post is the second installment in a three-part series that explains how Nedbank, one of the largest banks in South Africa, is rolling out the SEI’s Team Software Process (TSP)—a disciplined and agile software process improvement method—throughout its IT organization.  In the first post of this series, I examined how Nedbank addressed issues of quality and productivity among its software engineering teams using TSP at the individual and team level. In this post, I will discuss how the SEI worked with Nedbank to address challenges with expanding and scaling the use of TSP at an organizational level.

Read more...

Improving Software Team Performance with TSP

Team Software Process (TSP) 2 Comments »

By Bill Nichols,
Senior Member of the Technical Staff
Software Engineering Process Management

Bill Nichols In his book Drive, Daniel Pink writes that knowledge workers want autonomy, purpose, and mastery in their work. A big problem with any change in processes is getting the people who do the work to change how they work. Too often, people are told what to do instead of being given the information, autonomy, and authority to analyze and adopt the new methods for themselves.  This posting—the first in a two-part series—describes a case study that shows how Team Software Process (TSP) principles allowed developers at a large bank to address challenges, improve their productivity, and thrive in an agile environment.

Read more...