agile manifesto
 |
Why Teams Are Responsible for Successful Product Delivery Some believe that a large investment of time and money in requirements gathering and process oversight will lead to a more reliable or safer software product. But is that really the case? Steve Vaughn writes that in agile the team members are responsible for the successful delivery of their product. |
|
 |
A New Software Development Manifesto for Building the Right Things Author and software consultant Gojko Adzic recently gathered together a group of professionals to discuss software delivery and business outcomes, and to identify the core ideas that could be shared with delivery teams to help them focus on building the right things. |
|
 |
How to Choose the Right Communication Tool for an Agile Team Steve Berczuk explains how email and other tools of communication can have both advantages and limitations for an agile team. When making an absolute decision on whether to use a tool to collaborate, take time to observe and appreciate what works best for you and the people around you. |
|
 |
Can Capability Maturity Model Integration Coexist with Agile? Joe Townsend explores whether or not Capability Maturity Model Integration (CMMI) can coexist with agile. Remember that the Agile Manifesto specifically addresses processes, and the CMMi is, without a doubt, centered on process and documentation. |
|
 |
How Will Agile Software Practices Look in the Future? As agile adoption continues to gain popularity, it appears that Scrum is at the forefront of many agile implementations. Given the rise of Scrum, it makes sense that you might wonder how agile will continue to evolve as new methodologies—some of which may replace Scrum—are being developed. |
|
 |
Should Agile Teams Ban Telecommuting? Yahoo's Marissa Mayer recently announced a ban on telecommuting that has raised eyebrows throughout the industry. Agile teams tend to prefer face-to-face communication, so is a telecommuting ban appropriate for an agile team? It depends on the team and the situation. |
|
 |
Why Does the Agile Manifesto Ignore Testing and Quality? Joe Townsend revisits the Agile Manifesto and discovers that the words test and quality were never mentioned. What does this mean? Surely the original signatories of the Agile Manifesto had to have quality in mind when they met. Didn’t they? |
|
 |
How to Avoid Poorly Conducted Sprint Retrospectives The sprint retrospective is an important ceremony in Scrum. Of course, it’s bad if you don’t perform retrospectives at all. However, more often than not, it is not the retrospective itself, but rather a poorly conducted retrospective that results in an ineffective, stale, and meaningless effort. |
