A fantastic Google Tech Talk by Jeff Sutherland, one of the founders of Scrum, where he introduces Scrum, Agile and offers a lot of insight and guidance on how to scale Scrum e.g. the Meta Scrum.
In this Google Tech Talk, Hubert Smits provides some very useful insight on how to plan Software Development projects with Distributed Agile Teams.
Although I use this board to track our development programme across multiple products, teams and sprints, the Epic Board can also be a very useful project management tool. See The Epic Board – An Essential Project Management Tool.
I have taken the 7 Principles of Programme Management as outlined by the OGC’s framework for Managing Successful Programmes (“MSP”) and have attempted to elaborate upon them in the context of an Agile Environment.
I introduced the Epic Board as a programme management tool – a tangible release plan that can help you to plan software development programmes comprising multiple separate projects combined with Business As Usual Activities.
So, it’s no secret that one of the big benefits of ‘going agile’ is the ability/opportunity to track and optimise team performance.
The big question from a programme management and business perspective is:
How do you measure the operational costs/savings associated with improved efficiency or increased disruption within an Agile Software Development team?
There are numerous benefits to adopting Agile ideals and introducing Scrum/Kanban-esque practices at a programme level. One of these benefits is increased flexibility, which in turn offers improved output, reduced time-to-market and increased value.
So, the following questions are justified:
* What is Agile Programme Management?
* What is Agile Portfolio Management?
* Is it possible to efficiently and effectively manage a Programme of Software Development Projects in an Agile way?
The more I use the Epic Board, the more I love it.
Make no mistake about it, I don’t think this tool should (or could) replace a Scrum Task Board – it’s totally different…
The inspiration for this tool was the good old Scrum Task Board, a hugely useful Collaboration, Planning and Project Management tool. However, the strength and the limitation of Task Boards rest with the fact that they are focused at an iteration level. Cards on the board represent stories and tasks being addressed by a single team during a single iteration.
I have worked on quite a number of Agile projects (+100) over the past few years – usually taking on the role of either Scrum Master or Product Owner. I have worked on projects being delivered by a single team with one Product Owner. I have also worked on projects being delivered by multiple teams,