Developers commonly break user stories into tasks to facilitate distributing the implementation work across the team, and allow tracking of progress at a finer level of granularity. It seems perfectly logical.
Greetings,
A friend recently asked me what I saw going on in the agile world in 2008, and what we might see more of in 2009. I looked back through some of the things I wrote about this year and came up with this.
Organizations are not asking if they should use agile, they are asking how they can adopt agile practices. Accordingly, many of the agile thought leaders have moved from talking about why an organization should do agile to how to do it well. Here is an example drawn from Brain Marick's keynote at a recent conference. A related topic that I've heard often discussed this year is The Power of Done.
In the first program of its kind, students in Bowling Green State University’s Agile Software Factory program learn about agile development by building real software for local community service organizations. Over the course of a 16 week semester, students go from initial client meeting to delivery of a working system. The program is supported through a partnership with the Agile Alliance.
I was lucky enough to get to talk with Dr. Joseph Chao, associate professor in the Department of Computer Science and director of the Agile Software Factory at Bowling Green State University, as well as Phil Brock, managing director of the Agile Alliance, about the program. The result of that conversation is this article for InfoQ.
Cheers,
I have teamed up with Wayne Turmel, host of The Cranky Middle Manager Show, to create a 2-day workshop to help you move beyond being ‘good at your job’ to helping others excel at theirs. When we take this show on the road in 2009 the price will be $1,000 a seat, but we are holding a ‘dress rehearsal’ in Chicago on December 15 & 16, for a mere $450.
Learn more about the workshop
Claim one of the last available seats
Cheers,
Scrum has proven effective at promoting communication between members of a development team. The question of how to scale this high-bandwidth communication across teams, especially in large organizations, remains an area of active exploration and debate. Will Read has proposed a mesh-network inspired alternative to the popular Scrum-of-Scrums meeting for achieving this goal.
I found it interesting, and so I wrote about it for InfoQ. Read the article here.
Cheers,
A client recently asked me what blogs I read regularly. I pulled the list from my blog reader and here you go!
A recent discussion on the ScrumDevelopment list shed light on the ways in which agile development practices directly benefit the individuals involved. The consensus was that an environment ideal for individual growth can be created by the implementation of agile practices such as inspect-and-adapt, pair programming, test driven development, and constant collaboration and communication. I found the discussion interesting, and so I wrote about it for InfoQ.
Cheers,
In his keynote at the Agile Development Practices conference, Brian Marick described values missing from the Agile Manifesto. His view is that the Manifesto was essentially a marketing document, aimed at getting business to give agile a chance. Now that this goal has largely been achieved, an extended set of guiding values are needed to help teams deliver on the promises of the manifesto. I found his thoughts interesting and compelling, so I wrote about them for InfoQ. You can read the full article here.
Cheers,
Chris
My friend James Shore has declared agile to be in decline. He cites the many teams doing ‘sprints’ and stand-up meetings, without adopting any of the technical practices necessary to produce high-quality software over the long-haul. In his estimation, this has led to thousands of Scrum teams doing agile so poorly that they will almost certainly fail, and possibly take the agile movement with them.
I found the article interesting, and so I wrote this article about it on InfoQ.
Cheers,
Nonfunctional requirements describe qualities of a system (what it is) rather than its behaviors (what it does). Scott Ambler inspired much discussion when he recently asserted "Scrum’s product backlog concept works well for simple functional requirements, but… it comes up short for nonfunctional requirements and architectural constraints." in an article on Dr. Dobb’s Portal.
I reported on this for InfoQ, and you can read it here.
Cheers,