Blog on Agile principles, practices, and project management tools
Meaningful Agile
Set the stage in a retrospective
An agile retrospective is one of the most important ceremony in Scrum. There are lot of ways how to do it. We would like to provide to ScrumMasters and teams an overview how to do retrospective. And we are starting with Agile Retrospective: Set stage
Free ScrumDesk Read-only Licenses for Stakeholders
"As customer or stakeholder I do not want to wait two weeks to recognize the status of my project" Get customer on project board as chicken for free now! We, at ScrumDesk company, decided to provide free read-only licenses for your stakeholders or customers that needto have an access to your project stories, boards and plans. Such accounts will be automatically configured as Visitors in your projects. Read-only licenses [...]
ScrumDesk 5.0.3.37: Read-only licenses, Synchronization, Subversion
ScrumDesk In this release our team focused on improvements for administrators and user experience. Database Manager for SQL 2008 for SQL 2005 Administration Auto-assign of user license Licenses were necessary to assign separately from user accounts. In the new version, licenses are automatically assigned to newly created accounts. Administrators are still able to assign licenses according to needs as in previous versions. Missing license warning The user is [...]
Share, give and get free user license!
We are ready to share more value with you! Share following text on Twitter to earn 1 additional free user license valued for $220 "I use #ScrumDesk as our #scrum project management tool. You should check it out." To receive 1 additional free license your friends should refer the URL of your tweet in a registration form. What is in our offer? you earn 1 new license for [...]
Serious Play – accelerate your Agile transformation
Couple of weeks ago we were asked by organizers of Agile Meetups at Budapest to provide Agile Games talk. It was great opportunity to bring not just a presentation, but to really show how and why agile is good way of work. Agile transition is very often the current case in companies. Companies look for transition plans with measurable results. Unfortunately we see that even teams are promoted to [...]
Prepare Definition of Done together
As you are aware, Scrum is based on values very nice summarized by Mike Vizdos's o this cartoon. All of them, however, requires to define working agreement supporting creation of these values. An adaptation is in Scrum done at different levels, mostly through collaboration. Teams have to have common understanding, common vocabulary. We use word Done to indicate that work is completed. But what does it really mean? [...]
Product owner briefly
Product owner is a key role in Scrum framework. Companies used to start with intorudction of agile in development team, but the biggest mistake is missing preparation of Product owners before scrum/agile adaptation. Following slides pprovides fundamental information about Scrum and agile to Product owner role. Product Owner Briefly View more presentations from Dusan Kocurek.
ScrumDesk for Windows: User Story Template
Reaching a wider community is for us absolutely welcome not just because of numbers (either count or price). For us, the value is a knowledge of how scrum adaptation is done. It is very interesting to see how such a simple project management framework is adapted in so many ways. ScrumDesk development began as a materialized idea based on Scrum and XP from trenches book written by Henrik [...]
ScrumDesk and Subversion Synchronization
We would like to announce availability of Subversion synchronization hook. The hook synchronizes comments entered while committing changes into Subversion into ScrumDesk story comment. Read more and download the hook from the page Installation Guide.
Kano Model helps Product Backlog Prioritization
Product management is about searching for the most important requirement that needs to be delivered as the next. There are different prioritization practices. One such dimension that product owner should be aware of 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 the importance of stories by asking questions like [...]
Agile prioritization. What to build the first?
Product owner is often confronted with a large backlog. This post continues to explain how to consider priority of stories. See principles in previous post. Measuring risk and positive value allows to calculate the order in which stories should be developed. Very nice and simple visualization can be Risk vs. Value chart. Chart is split into four segments. Small dots represent stories. They are colored according to the status [...]
Business Value is not enough for Product Backlog Prioritization
Agile coaches teach teams to develop a business value that is delivered at the end of the sprint. But should be a value an indicator of the priority? Yes, but not the only one. There are many other attributes we often forget to consider. We suggest applying a different approach. We would like to have a possibility to calculate priority according to business value but considering risk and effort [...]
Scrum training
Are you looking for some ideas what Scrum is about? Check our training lesson we provided for more than 1.000 people in different IT companies of multiple business areas as telco, insurance, financial, startups, ISV, project, and product houses. Our training is about real-life experience, not just a presentation.
ScrumDesk Windows 5.0.2.34: Changes
ScrumDesk Windows v.5.0.2.34 changes ScrumDesk update v.5.2.0.34 contains the following important fixes: [*] [Task board] Additional fixes of tasks duplication in task board [*] [Task board] Sort by Id [+] [Administration] administrator is asked to enter company license key after login if there is no key entered [+] Yesterday's changes displayed in summary window upon start We would like to thank Ted for reporting.
ScrumDesk Windows 5.0.2.33: Changes
ScrumDesk update v.5.0.2.33 contains the following important fixes: [*] Tasks were duplicated once created [+] [Card] Simplified name of new task according number of tasks, not id We would like to thank Ted & Jan for reporting.