The Agile Manifesto extols the virtues of working software over documentation as a true measure of progress and business value. Teams in the early stages of agile adoption sometimes misinterpret this to mean that they should not write anything down. Other teams that are accustomed to waterfall and documentation-heavy methodologies continue creating extensive and redundant … Continue reading Lean Requirements with User Acceptance Test Cases
Year: 2012
Are You Being Agile or Doing Agile?
The starting point for adopting agile is for a team to learn the mechanics of an approach such as Scrum. They write user stories instead of use cases, do daily standups dutifully, and replace their lessons learned meetings with sprint retrospectives. Eventually the rest of the business comes on board, and the Product Owner takes … Continue reading Are You Being Agile or Doing Agile?
Is the Product Owner a Team Member?
Scrum prescribes three roles: Product Owner, Scrum Master, and Team Members. The Team Members consist of developers, DBAs, QA people, and others who do the coding, testing, and other work to bring software to life. Team Members rely on the Product Owner to provide information about requirements as well as to create and execute acceptance tests. If … Continue reading Is the Product Owner a Team Member?
A Swarming State of Mind
In a previous blog post, I discussed how sprint planning can help put the team in position to effectively swarm on tasks. If building software is like playing golf, sprint planning is akin to assessing playing conditions, determining yardage, selecting a club, and setting up to hit the ball. While the golfer has a few … Continue reading A Swarming State of Mind
Agile Reflections 
You must be logged in to post a comment.