Step 1: Define your project

Posted on 28, Sep 2010

This articles series is example how to start using SCRUM in your projects with help provided by ScrumDesk. Our example project will be a  RSS Reader, application that will provide easy access to RSS articles provided by many web sites. And we are starting right now… Who Product Owner Scrum Master 1. Login to ScrumDesk At [...]

Read more

Step 2: Define your development team

Posted on

Who Product Owner Work that needs to be done can be easy distributed in more development teams. ScrumDesk connects teams in one virtually connected social community. This community is notified by ScrumDesk notification system about any change. Teams can be distributed over the internet. New ScrumDesk project has one user at minimum, the author of [...]

Read more

Step 3: Define story templates

Posted on

In Step 3 we will define story templates according company process requirements. If your process is not requiring precisely defined steps, go directly to Step 4. Who Scrum Master Story Templates Is story templates required? No. But they are great when you have defined required development process steps. This is typically case for enterprise companies. [...]

Read more

Step 4: Planning project releases

Posted on

In this step product owner and development team will try to plan project releases. Who Product Owner Scrum Master Planning in SCRUM SCRUM is based on development in time boxes called Sprint. Sprint is a time needed to complete selected stories (features, bugs, requirements, tasks,…). Length of the sprint is typically 30 days, but it depends on a development strategy and [...]

Read more

Step 5: Planning project sprints

Posted on

In this step product owner and development team will try to plan project sprints. Who Product Owner Scrum Master Planning in SCRUM In Step 4 Planning product releases we defined sprint as time box for developers to complete selected stories. Product Development Product Backlog Release A Release B Sprint 1 Sprint 2 Sprint 3 ScrumDesk: Planning sprints [...]

Read more

Step 6: Backlog Stories

Posted on

In this step product owner and development team are going to plan project sprints. Who Product Owner Creating stories Target for this step is to create backlog stories. Product Development Product Backlog Stories in scrum are mainly created by product owner. As a first step let’s log in as product owner. Product owner is responsible for requirements specification and prioritization. [...]

Read more

Step 7: Planning Poker®

Posted on

In this step development team is going to estimate stories. Who Scrum Master Developers Planning Poker® Our backlog contains all known stories which has to be developed for product. Team sits down together around the table and they starts to discuss size of each story. Product Development Product Backlog Every developer will get cards with [...]

Read more

Step 8: Sprint planning meeting

Posted on

In this step product owner and development team will plan sprint. Who Product Owner Scrum Master Developers Visitors Sprint planning meeting Development team meats with product owner on sprint planning meeting. Product owner shows the team his plan for first sprint. Product owner chose stories by top importance (priority). Product Development Product Backlog Release A Sprint [...]

Read more

Step 9: Daily Scrum

Posted on

Who Scrum Master Developers Visitors Starting the sprint Scrum Master login to ScrumDesk before the Daily Scrum Meeting. The first thing he must to do is to start the sprint. To start it display SideView/Sprint and press big redStart sprint button. If sprint is started all  changes made to remaining and duration time, changes to stories state [...]

Read more