-
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 |
July 2004
|
Better Software
Tags: agile
I was honored to be the guest editor of a special issue of Better Software magazine that was focused on agile software development. This is my introduction to the issue (July/August 2004) in which I discuss looking for the one constraint that is holding back your project and how agile has shown us new places to look for (and eliminate) constraints.
Tags: agile
-
by Mike Cohn and Doris Ford |
June 2003
|
IEEE Computer
Tags: agile transitioning
The transition from a plan-driven to an agile process affects not only the development team members, but also other teams, departments, and management. In this article we describe common pitfalls and effective approaches to making this change.
Tags: agile transitioning
-
by Mike Cohn and Ken Schwaber |
January 2003
|
Agile Times Newsletter
Tags: agile management scrum ScrumMaster
Ken Schwaber and I co-wrote this article to help counter the misperception that agile projects do not need project management. The article outlines some of the responsibilities of the agile project manager.
Tags: agile management scrum ScrumMaster
-
by Mike Cohn |
May 2006
|
Better Software
Tags: agile transitioning
Change may be a constant, but it doesn't have to be constant. By following some simple guidelines, you can choose when and if you will allow adjustments to planned work during an iteration.
Tags: agile transitioning
-
by Mike Cohn |
April 2006
|
Better Software
Tags: agile
This tongue-in-cheek article offers humorous insight into the pitfalls of the waterfall process. You'll find yourself laughing at agile experts gone mad. You might even recognize some of your own company's policies taken to an extreme.
Tags: agile
-
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
-
by Mike Cohn |
January 2005
|
Cutter Consortium E-Mail Advisor
Tags: agile planning
We all crave regularity. We want a steady rhythm and a strong downbeat so we know the steps we need to take. This article explains how to give that sense of continuity to your software teams through fixed-length iterations, whatever length that is.
Tags: agile planning
-
by Mike Cohn |
October 2005
|
Cutter Consortium E-Mail Advisor
Tags: agile planning
With no land in sight to guide them, it would have been all too easy for early sailors to get lost in a seemingly endless sea. All too often, software projects also lose sight of when and if they'll reach their destination. This article explores what ancient mariners knew about navigation that we can apply to charting software project progress.
Tags: agile planning
-
by Mike Cohn |
October 2004
|
InformIT Network
Tags: agile user stories
At the surface, user stories appear to have much in common with use cases and traditional requirements statements. However, there are many subtle differences among them and many advantages to user stories, especially for agile development projects.
Tags: agile user stories
-
by Mike Cohn |
March 2006
|
InformIT Network
Tags: agile transitioning
A key consideration in adopting an iterative process is selecting how long your iterations will be. Mike Cohn discusses the issues to consider when determining whether your team's iterations should last two weeks, three weeks, or longer.
Tags: agile transitioning
-
by Mike Cohn |
May 2007
|
Scrum Alliance Website
Tags: agile scrum
Tags: agile scrum
![[Valid RSS]](/images/valid-rss.png?1214673064 "Validate my RSS feed"){kind=small}
