Agile Zone is brought to you in partnership with:

Mike is a certified PMP project manager and a certified ScrumMaster. Mike was involved with the creation of the DSDM Agile Project Leader certification, holds this certification at the Foundation, Practitioner, and Examiner levels. Mike was named an honorary member of the DSDM consortium and served on the board of APLN and the Lean Software and Systems Consortium. He currently co-leads the PMI Agile Community of Practice. Mike is a DZone MVB and is not an employee of DZone and has posted 126 posts at DZone. You can read more from them at their website. View Full User Profile

We Need a Shared Understanding

09.30.2013
| 2910 views |
  • submit to reddit

This post comes from Derek Huether at the LeadingAgile blog.

Earlier this week, I facilitated a backlog refinement meeting.  In the past, the team was used to the analysts completing all of the requirements in advance. The delivery team would then execute on those requirements. The problem, of course, was no shared understanding.

We came into the meeting with everyone agreeing they were on the same page.  That was true for about 15 minutes. The more we talked, the more they realized they were looking at things from individual perspectives.

At the beginning of the meeting, we had less than 10 user stories, from an analyst’s perspective. By the end of the meeting, we had a prioritized backlog with over 100 user stories at different levels of granularity.  They understand that it’s not perfect.  But, it’s a start.  For the first time, developers and testers were engaged at the beginning of the process.  At LeadingAgile, we call this the Product Owner team.  When the highest priority stories get to a “ready” state, they will be pulled into a delivery team’s queue.  Until then, we need to answer some of the more complicated questions, mitigate risk, and achieve that shared understanding.



Published at DZone with permission of Mike Cottmeyer, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)