-
by Martin Kearns and Mike Cohn |
May 2008
|
Better Software
Tags: 2008 teamwork
In seeking to improve how we develop software, we continually inspect
and adapt. While thinking recently about the characteristics of the ideal
team member, we found similarities between the best-performing soft-
ware teams of today and the Knights of the Round Table. This article considers the Code of Chivalry as applied to team members.
Tags: 2008 teamwork
-
by Mike Cohn |
February 2008
|
Scrum Alliance
Tags: product backlog user stories
This article addresses the issue of how much detail should be included in product backlog items and when that detail should be added. In answering that question it provides guidance on how to incorporate activities such as user experience design and architecture into agile projects.
Tags: product backlog user stories
-
by Mike Cohn |
January 2008
|
Agile Journal
Tags: patterns transitioning
There are many ways to transition to agile. This article covers six pairs of patterns that frame three decisions to be made at the start of the transition: Start Small or go All In, Iterative First or Technical Practices First, and Stealth Mode versus a Public Display of Agility.
Tags: patterns transitioning
-
by Mike Cohn |
May 2007
|
Scrum Alliance Website
Tags: agile scrum
Tags: agile scrum
-
by Mike Cohn |
February 2007
|
Scrum Alliance Website
Tags: scrum ScrumMaster
A discussion of six attributes that the ideal ScrumMaster should possess.
Tags: scrum ScrumMaster
-
by Mike Cohn |
October 2006
|
Scrum Alliance Website
Tags: scrum ScrumMaster
The selection of a new Scrum team’s ScrumMaster can impact the success or failure of the team's Scrum adoption. Choose the wrong person and the team could face the uphill struggle of trying to become self-organizing while under the thumb of a command-and-control style manager. Choose the right person—matching the skills of the new ScrumMaster with the initial needs of the team—and the team will have an incredible headstart in adopting Scrum.
Tags: scrum ScrumMaster
-
by Mike Cohn |
September 2006
|
Gantthead
Tags: agile contracts planning user stories
User stories are a great way to get people talking about requirements. However, there's a reason why we invented the written word: to make sure that nothing we've said is forgotten or misunderstood. This article explains why contracts are a good way to capture not only the user stories themselves but also to spell out what constitutes the successful implementation of each story.
Tags: agile contracts planning user stories
-
by Mike Cohn |
August 2006
|
Better Software
Tags: management metrics
Numbers may not lie, but mesaurements can sure mislead you. This article explores two myths about metrics and management and offers guidelines for devising project metrics that won't leave you broke and busted.
Tags: management metrics
-
by Mike Cohn |
July 2006
|
Scrum Alliance Website
Tags: planning scrum
Many teams try to divide and conquer when it comes to sprint planning, often with disjointed and disappointing results. This article explores why planning, like so many other agile practices, should truly be a team sport.
Tags: planning scrum
-
by Mike Cohn |
July 2006
|
Better Software
Tags: agile planning
If the only certain things in life are death and taxes, why do so many teams think that if they plan well enough they're somehow going to add software to that short list? This article deals with the mistakes team make when they try to account for every potential need and how best to plan for those things that users don't even know they want (or don't want).
Tags: agile planning
![[Valid RSS]](/images/valid-rss.png?1214673064 "Validate my RSS feed"){kind=small}
