A story of portfolio management evolution
This is the journey of a rapidly growing online wagering business from a small startup to a medium corporate. Like most businesses, our journey started grass roots: we transitioned from silo’d delivery teams to feature teams. We won’t talk about how we were growing the individual feature teams, but we will talk about how this change impacted our portfolio team and how we started to build a lean portfolio system, using some of the Lean enterprise principles.
We will talk about our challenges, what we did to overcome them and what we have learned and the journey ahead.
Outline/structure of the Session
Outline/Structure of the session
0-5: Introduction and setting the scene
5-20: Evolution of how we manage the portfolio: 3 challenges & learnings:
- Prioritizing & Planning customer features & larger projects
- Increasing complexity: increasing number of teams, more dependencies;
Portfolio governance framework:
- Disconnect between the strategic directions of the executive team and the sprint by sprint progress of the delivery teams.
20-25: Summary of learnings & next challenges/experiments to try
- An understanding of what challenges portfolio teams might face on their agile journey
- Tips for experiments on a portfolio level
Agile coaches, Leaders, Portfolio team members, Project managers, Programme managers
schedule Submitted 8 months ago
People who liked this proposal, also liked:
LJ Kenward - Junior Developers - The Next GenerationLJ KenwardJunior DeveloperXero
schedule 8 months agoSold Out!
Demand for technologists is fast becoming unfulfillable. The pool of talent is drying up, with the oldies heading into retirement, management or just straight up senility, it is never a more important time than now to grow the next generation of technologists!
I'll take you on the Junior Developer journey with me, from justifying why Juniors are good for business, how to help them jump In and level up when they first join a team, and then how to continue developing their skills and career throughout their journey.
I'll talk problems, benefits, hints, how to use agile to help make the process painless and prosperous, based on a combination of personal experience, local research, and industry practises, plus some ideas a little left of centre.
Wai Ling Ko - Five things I learned about Scrum while becoming a trainerWai Ling KoScrum MasterLiberty
schedule 8 months agoSold Out!
In 2008, I became a Scrum Master at a large Dutch Bank. I was sent to Scrum training and I learned how to 'read' and adopt the Scrum Guide. During my journey as a Scrum Master, I worked with different teams (distributed and local) in organizations big & small. Last year, I decided to become a Professional Scrum Trainer and it was during that grueling track that I again learned more about Scrum, and myths got busted and misconceptions were unraveled.
In this talk I will reflect back on my experiences and share five things I have learned about Daily Scrums, Done, Sprint Goal(s), Sprint Reviews and myths.