If the Agile Manifesto prefers responding to change over following a plan, it is not against planning. In this article, Raju Kidambi explains why it is important to use Scrum during the pre-project planning phase.
This presentation will help you understand what it takes to run a successful agile release planning meeting. The release planning is the “pacemaker” of enterprise agility and the Agile Release Train (ART) which aligns the Agile program to a common mission. Based on nearly a decade of experience, Dean Leffingwell and Scaled Agile have developed a process which has worked with small trains of 40 people to larger trains of 180. This video explains what it takes to run a successful Agile release planning meeting from a scaled point of view (100′s of teams).
User stories and their size are often the basis for planning a Sprint in Scrum. You can use a relative estimation and planning poker or a more classical approach to define the effort for each user stories. As such, they are also the basis for the metrics of progress and the velocity of the Scrum team.
If Agile approaches are tools that allows to deal with uncertainty and change, they have often little impact on the management mindset that still requires to have deadlines proposed with software development projects. In this blog post George Dinwiddie discusses the usage of user stories for planning in Scrum projects.
In this article, Christophe Le Coent discusses how you can express a Scrum product backlog to provide enough planning information to management but still following the Agile principle that “welcome changes over following a plan”.
How do agile projects accurately forecast their budget when they are typically just a bunch of hippies coding without requirements or documentation? Waterfall projects are obviously much better at budgeting with all of the traditional up front design and planning, right? Anyone who has been on a waterfall project can see that this is a complete fallacy.
In this article, Vaidhyanathan Radhakrishnan discusses about the value of release planning in Scrum. This is the tool to schedule timelines for a project or a product in a complex environment where the outcome of one team is required for the other teams. The article proposes an approach to produce a release plan. This approach is based on the finding primary and secondary features in the product backlog. You can then determine whether the resources are adequate and what interdependencies exist to adjust the feature layout. The article presents the advantages of a release plan and the common disadvantages of this situation, like including ongoing or generic activities spread across the timelines which dilutes the focus of the plan.