By using an approach similar to that used by surfers to catch waves, you can effectively help your team transition to agility. Scott presents a four-stage process that alternates training with coaching and doing with learning.
Introducing a full agile framework can be daunting and cumbersome. Instead, try beginning with the method's core focus: continuous improvement. Retrospectives are the starting point of your agile journey and can help you solve the most immediate problems in your process, leading you down the road of process improvement.
Program planners in IT organizations have a dilemma: On one hand, their agile teams tell them that if requirements are defined up front, agile teams cannot operate; but on the other hand, the program’s budget and scope need to be defined so that resources can be allocated and contracts can be written for the work. How does one reconcile these conflicting demands?
Thomas Wessel presents how T-shaped and pi-shaped teams based on each member's span of knowledge, ability to collaborate, and depth of expertise play an important part in how effectively your team performs.
There are a surprising number of similarities between successful World Cup and agile teams. Both must be diligent in four areas in order to reach their “goals.” This article explores the parallels between the two for selecting the team, getting up to speed, consistency, and game plans.
The death spiral supersedes the death march in that the death march is a singular event, whereas the death spiral is systemic. It is the result of organizational dysfunction where teams march toward deadline after deadline without reflecting on or questioning if there is a better way to deliver software. There is! Take these positive steps.
Agile is growing up and is now officially a teenager. It has moved from being a somewhat rumbustious child with some overzealous followers and a skeptical management crowd to something that is generally accepted by the mainstream IT community and particular management. Has the agile community lost something? Are the founding members and early practitioners evolving the practice? Is this good? Well, the answers are yes, yes, and maybe.
The framework for agile development empowers the diverse environments of modern business. While some project teams can be collocated, many projects are undertaken by teams who are distributed geographically or organizationally. This article focuses on five challenges faced by these distributed agile development teams and provides some solutions.
"Don't bring me problems; bring me solutions." Sound familiar? Sounds like a management cop out to Johanna Rothman. A primary purpose of managers is to help their teams perform to the best of their abilities, and that includes stepping up and making tough decisions to help solve problems.
Team members involved in hopeless projects become dejected, stressed, and overworked. Are there any silver linings to working on a doomed project? This article argues that there are. When you and your teammates are stretched to your limits, you can learn a lot about each other, your managers, and what it takes to make a successful product.