Starting an Agile project in a gated Enterprise environment
You work for a company that until now has been delivering projects following Waterfall. Your new project is asked to be delivered in an Agile way. You know some basics on what Agile is, the need for frequent deliveries, focus on value, self-organizing teams where people collaborate, empirical planning, etc. What now? Where do you begin with your very first Agile project? What to do to get things going and deliver fast?
I will bring my experience on different Enterprise environments and the approach I have taken when working with teams new to Agile development. How Agile transformation was applied in the organization and how was translated at the project level. Some of the tools and techniques I will talk about are Project Canvas, Value Stream mapping, Story mapping, etc. Through a workshop, participants will have an opportunity to learn how to apply these tools and techniques right away to their Agile projects. These tools and techniques are valuable even for teams that are already running Agile and want to find ways to improve.
This is a hands on workshop that will take you through the different steps of initiation, preparation and getting ready for Sprint 1. You will experience how to do just-enough planning, estimation, architecture and feel confident to deliver value on Sprint 1. You will gain knowledge and experience that you can take it to your teams right away. This is knowledge that you can use when you start a new project or a new release. You will work on some real project, but feel free to bring your project and plan it with us!
Outline/Structure of the Workshop
60 minutes: presentation, setting context, showing some examples and previous experiences
30 minutes: preparation for the workshop, creating teams, assigning roles, deciding on the project to work on
20 minutes: project canvas walk through, explanation and preparing for the exercise
40 minutes: each team works on the project canvas. Recap at the end sharing thoughts and insights
20 minutes: Story mapping walk through, explanation and preparation for the exercise
40 minutes: each team creates story mapping for their project. Recap at the end, sharing thoughts and insights
10 minutes: How to do high level estimation using story mapping
20 minutes: each team does a high level estimation for the items on their story map
10 minutes: how to plan releases, how to organize the work and understand the incremental value delivered
40 minutes: each team creates the release plan, a set of incremental products and a vision of the product growth
10 minutes: Plan the release of the first deliverable, identify risks, spikes, etc
30 minutes: Each team focuses on the first release, identifies risks, what areas they need to run spikes, etc and create a plan for those
10 minutes: What is team agreement and how to create one
30 minutes: Each team will work together to create a team agreement regarding not only the process but also their communications, environments, etc
10 minutes: Sprint 0, why, what we do, bring up to speed new team members identified, etc
30 minutes: each team will simulate certain activities done, such as creating a team agreement, a training session for the new members, running a couple of spikes as per what we have identified previously, etc
10 minutes: preparing for sprint 1, sprint planning, standups
40 minutes: each team will simulate a sprint planning session and a standup session
20 minutes: regroup, recap, discuss, share insights, discuss roles, lessons learned, etc
- Attendees will leave with hands-on experience on some tools and techniques to accelerate learning at the team level, that they will be able to apply during the initiation of Agile projects, such as Story Mapping, Project Canvas, Value Stream Mapping, etc. I will also touch on the Sprint 0 concept that is used to prepare the environment and other prep work before Sprint 1.
- By using these tools, they will leave with a learning model that is empirical and incremental. For instance, how to generate project scope from the project goal (through Project canvas), how to identify system changes based on the project scope (Value Stream) and how to organize the work from the changes identified, into an overall release plan (Story Map)
- They will also learn tips&trick on how a Story Map can be used to generate resource plans and project forecasts
Scrum master, Product Owner, Business Analyst, Team member, project manager