In my last blog post, The most badly implemented, yet most critical, technique in agile projects, I briefly mentioned discipline as being important. In this post I explore this further and dispel a couple of myths associated with Agile development.
How is your Agile or Scrum project going? Is it truly delivering agility to your organisation in the way that the Agile Manifesto or Scrum Guide intends?
When an organisation is making an investment decision for a project, they want confidence that the investment will deliver the benefits they are seeking. A business case sets out important information to help decision makers make the right investment decision for projects. However, the decision is only as good as the information that the business case provides. A better business case will lead to a better investment decision. To help your organisation deliver better business cases, in this Blab we discuss the question 'What makes an effective business case?'.
Don’t you love it when you attend a business meeting that starts energetically and on time, the attendees are really present and actively discussing the agenda, resulting in clear decisions or action points? After a meeting like that, I walk out enthused, knowing work has been done well.
The ‘sprint-backlog’ is those user stories a development team plans to commit to during a Scrum sprint. And if you are following the Scrum Guide it is up to the development team (and only the development team) to assess what capacity of work can be accomplished over the upcoming sprint.