The agile backlog is now a pretty ubiquitous feature of development projects. We know and understand how important it is to prioritise it by business value and we look to the Product Owner to make these critical decisions for us. After all, they are in a position to understand what work needs to be done to best meet our business needs, which obviously also encompasses our user and stakeholder needs.
Explaining my role of Scrum Master to a non-agilest can be somewhat challenging and I often end up digging up the classic “Servant-Leader” description. While vague, it does help communicate the difference between Scrum Masters and other people-managers.
JIRA and Trello are both common tools used by Agile development teams.
If you are using JIRA or Trello on your project, do you need to print out user stories from these tools for your physical Scrum or Kanban boards? If so, are the standard JIRA, Trello or associated plugin facilities meeting your printing needs?
In this article I work though how you can customise and print JIRA and Trello user stories to meet the needs of your project and project team.
Monte Carlo simulations can be used on Agile software development projects to manage uncertainty and reduce risk when determining the likely time cost and time estimates for the project. Monte Carlo simulations involve mathematical modelling and this is normally performed in Microsoft Excel or similar spreadsheet software.
All projects have risks. The success of a project can often be dictated by how well the project team manages that risk.
Last month Equinox IT training partner and Certified Scrum Trainer Rowan Bunning delivered a webinar with us entitled Using Agile techniques to manage risk more effectively. The webinar covered a lot of ground and was very well received. In this article I summarise some of Rowan’s key takeaway messages.