Scrum Ways of Working

23 Mar 2022 | Agile Culture

It is quite common (and important) to define the ways of working for a new team. Many of the teams I work with use Scrum. So, I have been using the following google slides presentation to go over the team ways of working and document it.

 

>> download/copy the Scrum WoW google slides presentation for your usage

Please find below the text on the slides.

Ways of Working  (WoW) for a SCRUM TEAM

  1. CADENCY
  2. MEETINGS
  3. PRODUCT BACKLOG
  4. SPRINT BACKLOG
  5. DOR (DEFINITION OF READY)
  6. DOD (DEFINITION OF DONE)
  7. TEAM RESPONSIBILITIES

Please fill up / change the <marked items>

 

Cadency

  • We will work with Sprints of <one week>
  • Any changes in the team or in the work backlog are informed in the weekly planning meeting

 

Meetings

  • Daily meeting: every weekday from <10 to 10:15 CET>
  • Weekly planning meeting: every Monday from <10:30 to 11:30 CET>
  • Weekly review meeting: every Friday from <10:30 to 11:00 CET>
  • Weekly retrospective: every Friday from <11:0 to 11:30 CET>

 

Product Backlog

  • We will follow the product backlog order, as per <LINK: e.g. Lean Inception Mural>
  • The product backlog has items of higher level of abstraction (such as features and epics) which still need more clarification before considering Ready to be worked on. These higher-level items might change as per business changes and user feedback.

 

Sprint Backlog

  • We use DoR (Definition of Ready) to inform an item is ready for development, so it enters the Sprint backlog
  • We use DoD (Definition of Done) to validate the work on the item is complete (done!) so it leaves the Sprint backlog
  • The Sprint backlog is defined in the Sprint planning meeting
  • Our Sprint backlog is available at <LINK: e.g. Jira>

 

DoR (Definition of Ready)

The work item …

  • is represented by a User Story
  • is covered by acceptance criteria
  • is mapped to an interface (when necessary)
  • dependencies are identified (if any)

<please adjust to your team definitions>

 

DoD (Definition of Done)

the work item …

  • delivers an increment of the product
  • complies with the established acceptance criteria
  • is documented for use
  • adheres to the coding and technical standards
  • maintains product performance indices

<please adjust to your team definitions>

 

Team responsibilities

  • <PERSON> is the primary person of contact to ask about any changes in the backlog and the direction of the product
  • <PERSON> is the primary person of contact to ask about any technical aspect about the product
  • <PERSON> is the primary person of contact to ask about any project / process improvement:

<please add to your team definitions>

 

 

Feel free to copy, to use, to share and to change this content, but please keep a link to caroli.org/en/scrum-ways-of-working  , so other people find it as well as the future updates.

Paulo Caroli

Paulo Caroli is the author of the best-selling book “Lean Inception: How to Align People and Build the Right Product” (the first on a series of books about Lean Strategy and Delivery). He's also the creator of FunRetrospectives.com , a site and book about retrospectives, futurospectives and team building activities. Caroli writes on this blog frequently. Receive the next post in your email. Sign up here .

Pin It on Pinterest

X
X
X