Posted on 21, Feb 2012
You know that probably. Requirements are coming, coming and coming. There is no time to stop and think about them. There is no time to organize them. There is no time to analyze your backlog so you know which requirements should be developed as next. Even more, many customers ask you of new functionality or defect fixes. In our [...]
Read morePosted on 30, Dec 2011
While being in agile transition, teams look for information how to do agile correctly. Often the question sounds ’How to DO agile?‘ The guideline we prepared might be helpful to shorten your transfromation period and stabilize agile environment earlier. Download full paper as PDF from http://www.scrumdesk.com/Download/Documents/AgileResources/ScrumGuidelines.pdf Scrum Guidelines View more documents from ScrumDesk
Read morePosted on 18, Jul 2011
One customer asked us an interesting question regarding relations of stories in ScrumDesk. What ScrumDesk supports now is simple relations tracking solution. Very simple and basic functionality – possibility to track, see and print out it in documents. For the first look some basic functionality in ScrumDesk is missing. Functionality similar to Gannt chart way [...]
Read morePosted on 30, Jun 2011
Pig & chicken Metaphor that helps to distinguish people actively involved in development of the product and people who should not interrupt the team iteration. Product Owner Father of the product. Responsible for product success. Providing vision to team. Communication channel between the team, stakeholders and customers. Responsible for: product requirements, prioritization, stakeholders management driving [...]
Read morePosted on 28, Dec 2010
Our previous blog posts were about core product ownership approaches how to prioritize backlog according to business value. Another dimension a product owner should know is expected customer satisfaction. Satisfaction with developed feature or story. Mr. Noriaki Kano developed Kano model as valuable technique helping to recognize that. Applying this method the product owner can identify importance of stories [...]
Read morePosted on 28, Sep 2010
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 morePosted 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 morePosted 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 morePosted 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 morePosted 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