ScrumMaster™ DEMO File

Jump right into ScrumMaster Agile project management with this pre-built project file.

Evaluate how ScrumMaster best meets your needs: use the simple project data to explore and practice with ScrumMaster’s basic functions.  Prefer to build your own project from scratch?  Simply delete the DEMO file and start a new project.

Download the DEMO Project File

Download the Demonstration Project file from the new Get more menu item (cloud icon in the ScrumFunction menu bar).

Get more stuff for ScrumMaster™

Get more for ScrumMaster™

ScrumMaster Project Management Demo

Click to download ScrumMaster project management DEMO

Team, Topics (Requirements) and Milestones

Swipe to view the Team, Topics (Requirements) and Milestones screens.

The imported project data lets you immediately view the Burndown graph, Sprint History charts, and Reports from the project’s home page app bar.  (Click each to see the related posts for more discussion on purpose and use.)

Backlog: Stories and Tasks

DEMO Stories and Tasks

DEMO Stories and Tasks

At project start:  240 story points and 6 sprints

  • Sprint definition = two weeks, 5 days per week, 8 hours per day
  • Set ‘When is a task done?’ = ‘Test complete
  • Average cost per team member = $100
  • Set 4 team members = ‘Work effort reduces backlog
    • Estimates team development costs for project in Burndown graph
  • Project = 6 stories, 4 tasks per story, estimated story point value (SPV) = 10 SPV per task
  • Target Velocity held at 40 story points per sprint throughout project, other variables change (see table)
  • Each story references a Topic (Requirement)

Sprint Planning, Daily Standups, and Retrospectives

Real life is never this simple, but let’s conduct our sprints as follows and see how ScrumMaster handles the results.

Assume a two week sprint, team meeting approach is used which includes an initial Sprint Planning meeting on Monday, Daily Standups to change task status through the end of the sprint on the following Friday, followed immediately by a Retrospective meeting.

Two Week Sprint Meeting Pattern

Two Week Sprint Meeting Pattern

Because any meeting time is real work completed and adds project cost, ScrumMaster adds a minimum of 1 story point per meeting.  The actual number of story points added to the backlog for a meeting varies, depending on number of team members attending whose work effort reduces backlog and how long the meeting lasts.  See the clock in the upper right hand corner of the app bar?  It’s a reminder that meeting time is money… and ScrumMaster automatically tracks a story point value (SPV) to capture that cost for you.

Typical Two Week Meeting Pattern (adds minimum 11 new story points per sprint)

To make it easy for you to see ScrumMaster in action, each sprint has been given unique conditions (table below).  Refer to the table when analysing how the data results display in the Burndown graphs, Sprint History charts, and Reports.  Get familiar with how ScrumMaster works and then add your own data in Sprint 6 to test the result.  Add stories and tasks, change target velocity, add and change team member status.  Add more tasks along the way-in Daily Standups or completed work spikes in a Retrospective.  Take partial credit for work complete in the Retrospective.

DEMO Project Work Assumptions

DEMO Project Sprint Assumptions

DEMO Project Sprint Assumptions

Please drop us a line and let us know how it goes.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s