Where Dashboard Fits

We manage our Sprints via this Dashboard. The interactive graph V² Agile Layer Model below shows where Sprint (Dashboard) fits in. Click on each layer to learn how it works.

Scrum Boards

V² Scrum Board

• Public → Scrum Board V²
• All activities of this weeks sprint
• Listing of what goes into next spring and the spring after that
• listing of what we are working on right now

Production Scrum Board

• Public → Scrum Board Production
• Listing of all production issues, grouped into 4 columns:
  • Design
  • Production
  • Bring to Life
  • Shipping / Closing

Understanding V² Sprints

If You are Familiar with Agile Sprints

• → Weekly Sprints Overview (on page links are broken → Bug: Stop Angular from Rerouting Hashtag #154
• → V² Scrum Board of all Work
• → V² Scrum Board Production Only
• Sprint Kick Off: Sunday 8:30 pm Las Vegas Time, Monday 11:30 am China time
• Daily Stand Up: 8:30 pm Las Vegas time, 11:30 am China time
• Sprint Review: At the bottom of each completed weekly sprint. → Example Sprint Review

If Agile Sprint is new to you

We are working on a detailed Article Series → V²Plan Agile System. A Quick Start Guide goes like this:

Sprint Kick Off Meeting

• Preparation (1 hour prior to meeting)
  • Update Messgae: Scrum Master notifies Team Members once Sprints Overview and Scrum Boards are updated.
  • Study Weekly Sprints: Every Team Member studies a) the updated → Weekly Sprints Overview and b) the updated → Scrum Board V² and → Scrum Board Production to understand targets and issues for this and next two sprints
• Meeting (Skype call on Sunday 8:30 pm Las Vegas Time, Monday 11:30 am China time)
  • Sprint Review: Discuss the results of Sprint Review. → Example Sprint Review
  • Sprint Targets: Discuss agreements / disagreements with the next three Sprint Targets
  • Discuss Problems: Every team member already read the target of this week’s sprint and her / his assignments. Only problems need to be discussed.
  • First Stand Up Meeting: Each developer presents last Friday’s work and drags the work of today into Developing column.
  • Wrapping up: Any last minute comments? Compliments or Complaints? Confirm next Kick Off Meeting on schedule?

Daily Stand Up Meeting

At the beginning (or end) of every work day the sprint team meets for the Daily Stand Up Meeting. Each developer has 2 minutes to show what he did since the last meeting and what he is going to do until the next one. The idea is to synchronize order in which tasks are worked down to avoid one incompleted issue is gating another. This is also the best place to ask for help if needed. During the meeting the agreed upon next work is dragged from the This Sprint column to the Developing column.

Working Down Issues

Every day each developer works down the issues assigned to him and placed in the Developing column of the Scrum Board. In case he finishes early he drags another issue from This Sprint to Developing and works it down.

Sprint Preparation

At the end of each Sprint the Srum Master cleans out the Scrum Board like so:

• Work on Sunday and possibly Monday morning. So far I (HC) needed about 14 hours work time.
• Archiving all closed Issues → Example Closed Issues
• Create Sprint Review → [Example Sprint Review](#example-sprint-review}
• Close Issues that the developer finished but forgot to close
• Move still open issues from Developing to This Sprint column. Add lable: o.week.2 to mark failed target.
• Reorganize and update Weekly Sprints Overview
• Move Issues from Next Sprint to This Sprint
• Move Issues from Sprint after Next to Next Sprint
• Fill up Sprint after Next from Backlog
• Order Issues in all columns so that more important issues or issues gating others are placed on top
• Open each issue. Check if:
  • Writing is complete and up to date
  • Labels, Milestones and Assignee are properly
  • Only one Assignee is set
  • Task have trigger build in to keep flow on hand over work (e.g. write “@bcaswelch Please review” in comment)

Creating Sprint Review

After each Sprint (and prior to the next) the Scrum Master creates the Sprint Review like so:

• Add search term of current week into Issue Title. Example for label: “16W23” as 2016 week 23
• Create Link as → [Example Closed Issues]{#example-closed-issues}
• Create Statistics → Example Statistics
• Write the Wish List for Improvements
• Notify team members that all reference documentation to new sprint has been updated so they can prepare next sprint

Weekly Sprints Overview

Purpose of Weekly Sprints Overview

• Give an Overview of the current plus next two sprints
• Keep a historic record on what we did in each week and what we learned to improve each week
• Compile targets for next two sprints before the Scrum Master spells it out in current sprint

Sprint Week 26 (June 27) — In two weeks

Focus Sprint after Next

Sprint Week 25 (June 20) — Next Week

Focus next Sprint

Sprint Week 24 (June 13) — This Week ← ←

Focus this Sprint

Sprint Week 23 (June 6) — Last Sprint

Targets of Sprint 16W23

Sprint Review

Statistics

• (*1) One Epic contains the in average work of 8 Normal Issues.
• (*2) This number is misleading. V²Shop-Midwest worked on many Articles. But the Issue not closed yet. We should discuss to a) change these Issues to Epics, b) if we should break the Epic into separate issues for more transparent Management?

Improvement Wish List for Next Sprint

• Meetings on Time or change of time is announced 2 hours earlier
• Notification Chat Period: 9:00 … 10:00 am China time, 6:00 … 7:00 pm Las Vegas time
  • During this one hour everybody responds notifications with the speed of chatting

• Answer all Notifications at the end of the day

• → All issues closed in Sprint of Week 16 {#example-closed-issues}