![The Agile Lean Gardener](/img/default-banner.jpg)
- 87
- 500 815
The Agile Lean Gardener
United Kingdom
Приєднався 16 бер 2022
This channel is focussed on providing practical ways of improving your agility in business and covers Agile & Lean ways of working as well as Flow and Servant Leadership and frameworks like Scrum, Kanban & eXtreme Programming.
I’ve been a Scrum Master and Agile Coach for over 20 years, working with companies such as Schroders, HSBC, Lloyds Banking, RBS, Thomson Reuters, SapientNitro, Nationwide, BP and more. I provide consultancy services so please contact me on Stephen.Angood@SPA-Agile-Consulting.co.uk for more information.
I offer personal coaching and mentoring please visit my website for subscription pricing and plans.
I’ve been a Scrum Master and Agile Coach for over 20 years, working with companies such as Schroders, HSBC, Lloyds Banking, RBS, Thomson Reuters, SapientNitro, Nationwide, BP and more. I provide consultancy services so please contact me on Stephen.Angood@SPA-Agile-Consulting.co.uk for more information.
I offer personal coaching and mentoring please visit my website for subscription pricing and plans.
Supercharge your Scrum & Kanban delivery
People often find that after adopting Scrum or Kanban they aren't getting the kind of performance they expected or were told they would get. It can become very frustrating and sometimes leads to teams dropping the frameworks. This video explores 5 techniques you can use to supercharge your delivery no matter whether you are using Scrum or Kanban - or any other framework, process or methodology for that matter. This video discusses Flow which is a post Agile concept focussed around the delivery of value. If you're working in an Agile way using Scrum or Kanban you need to understand the principles of Flow to supercharge your delivery. Here I explain what Flow is and detail the 5 core underlying principles that will help you deliver in a faster and better way.
For consultancy work please contact me at Stephen.Angood@SPA-Agile-Consulting.co.uk
Join my channel through memberships to get access to perks:
ua-cam.com/channels/vPh9FG4XhbbURs0HmCbdug.htmljoin
For personal coaching/mentoring check my website for subscription plans.
www.spa-agile-consulting.co.uk
Buy Me A Coffee:
www.buymeacoffee.com/theagileleangardener
Follow me on LinkedIn:
www.linkedin.com/comm/mynetwork/discovery-see-all?usecase=PEOPLE_FOLLOWS&followMember=stephen-angood-8703444
Related videos:
Cycle time, percentiles and Monte Carlo Simulation
ua-cam.com/video/hQOs5CfkOJU/v-deo.html
Story points, velocity & burndowns - There is a better way!
ua-cam.com/video/kRU26kvtdDo/v-deo.html
Reduce cycle time with flow efficiency
ua-cam.com/video/B2R6tNFgwkU/v-deo.html
Ageing work in progress charts
ua-cam.com/video/EhVgeL_t98E/v-deo.html
How to create a macro in Excel to run Monte Carlo Simulation
ua-cam.com/video/LBFBpMtZ4qo/v-deo.html
How to extract data from Jira for cycle time and Monte Carlo Simulation using EazyBI & TIS
ua-cam.com/video/5Szv-w6n5NE/v-deo.html
The secret behind the definition of done in Scrum
ua-cam.com/video/hc49S8vJ-sw/v-deo.html
How to create a product backlog quickly
ua-cam.com/video/iR-Lv2QyxF8/v-deo.html
How to be a leader “If” you’re young - Part 1
ua-cam.com/video/wId_p8qw0aI/v-deo.html
Top 5 reasons why agile transformations fail
ua-cam.com/video/_Ye_i2MwAgM/v-deo.html
Why you need to go Agile in 2022 before it's too late...
ua-cam.com/video/CYoSpUQCx-M/v-deo.html
How to build better relationships and the physics behind it
ua-cam.com/video/JIZL1y2tjWw/v-deo.html
The secret behind the definition of done in Scrum
ua-cam.com/video/hc49S8vJ-sw/v-deo.html
#TheAgileLeanGardener
For consultancy work please contact me at Stephen.Angood@SPA-Agile-Consulting.co.uk
Join my channel through memberships to get access to perks:
ua-cam.com/channels/vPh9FG4XhbbURs0HmCbdug.htmljoin
For personal coaching/mentoring check my website for subscription plans.
www.spa-agile-consulting.co.uk
Buy Me A Coffee:
www.buymeacoffee.com/theagileleangardener
Follow me on LinkedIn:
www.linkedin.com/comm/mynetwork/discovery-see-all?usecase=PEOPLE_FOLLOWS&followMember=stephen-angood-8703444
Related videos:
Cycle time, percentiles and Monte Carlo Simulation
ua-cam.com/video/hQOs5CfkOJU/v-deo.html
Story points, velocity & burndowns - There is a better way!
ua-cam.com/video/kRU26kvtdDo/v-deo.html
Reduce cycle time with flow efficiency
ua-cam.com/video/B2R6tNFgwkU/v-deo.html
Ageing work in progress charts
ua-cam.com/video/EhVgeL_t98E/v-deo.html
How to create a macro in Excel to run Monte Carlo Simulation
ua-cam.com/video/LBFBpMtZ4qo/v-deo.html
How to extract data from Jira for cycle time and Monte Carlo Simulation using EazyBI & TIS
ua-cam.com/video/5Szv-w6n5NE/v-deo.html
The secret behind the definition of done in Scrum
ua-cam.com/video/hc49S8vJ-sw/v-deo.html
How to create a product backlog quickly
ua-cam.com/video/iR-Lv2QyxF8/v-deo.html
How to be a leader “If” you’re young - Part 1
ua-cam.com/video/wId_p8qw0aI/v-deo.html
Top 5 reasons why agile transformations fail
ua-cam.com/video/_Ye_i2MwAgM/v-deo.html
Why you need to go Agile in 2022 before it's too late...
ua-cam.com/video/CYoSpUQCx-M/v-deo.html
How to build better relationships and the physics behind it
ua-cam.com/video/JIZL1y2tjWw/v-deo.html
The secret behind the definition of done in Scrum
ua-cam.com/video/hc49S8vJ-sw/v-deo.html
#TheAgileLeanGardener
Переглядів: 154 095
Відео
How to deliver more value using the 80 20 rule
Переглядів 2784 місяці тому
Agile advocates maintaining simplicity but how do we do that with complex problems? Maintaining simplicity is perhaps the least understood of all the agile principles. But without focusing on this it's likely that you're working on the wrong thing. Maintaining simplicity is really about maximising the amount of work we don't do which is where the 80 20 rule comes in which you might know is base...
Power the flow of your work with flow efficiency
Переглядів 4574 місяці тому
What is flow efficiency? Understanding your flow efficiency is a great first step to improving your cycle time and forecasts with Monte Carlo Simulation, particularly if you’re starting out with flow metrics. It helps you identify problem areas with your process and apply interventions to improve. This video shows you how to calculate it and what to do once you know what it is. For consultancy ...
Stop estimating start forecasting with Monte Carlo Simulation for better predictability
Переглядів 8284 місяці тому
Estimating in Scrum or Kanban with story points and velocity is a waste of your time. In fact estimation itself is pointless, estimation is evil! No estimates is where you want to be. Instead you need to make data driven decisions based on your empirical data and start forecasting with Monte Carlo Simulation to become more predictable and provide leadership with better data and increase trust a...
When to use Kanban over Scrum?
Переглядів 9594 місяці тому
If you’re using Scrum but constantly fail to see any benefit then it’s likely that Scrum isn’t the right framework for you and you should consider a switch to Kanban. But how do you know when and why it’s time to make that switch? Well, there are 14 tell tale signs that will help you make that decision and this video discusses them all. For consultancy work please contact me at Stephen.Angood@S...
How to fix Scrum when it’s not working and broken
Переглядів 4795 місяців тому
Are you finding that Scrum isn’t working for you? Do you constantly find that you’re never quite able to complete your sprint backlog? And even when you get close it never really feels like success. You’re more of a feature factory than anything else. Well it’s almost certainly down to one thing you’re not doing. It’s easy to fix scrum by starting to do this one thing which is the subject of th...
The secret to running a successful project
Переглядів 6155 місяців тому
Most projects suffer from the same thing, slow decision making and even then the decisions made are bad ones. This is called decision latency and is the number one killer for projects. Decision latency is the average amount of time it takes to make a decision but not only that, it’s the quality of that decision too. In this video I discuss what decision latency is and the effect it has on proje...
Extract data from Jira free native no apps for cycle time
Переглядів 9015 місяців тому
This video walks you through step by step how to add cycle time data in Jira and how to export it. Free and native no apps or add ons required. It requires adding some custom fields, a screen update and then using Jira automation and Jira smart values. Finally a free and easy way of getting the data you want out of Jira to allow you to start using Flow Metrics in Jira without having to buy expe...
Thank you to everyone who's subscribed!
Переглядів 2035 місяців тому
Thank you for all your support over the last 2 years, it means so much to have such amazing support from you all, thank you. Join my channel through memberships to get access to perks: ua-cam.com/channels/vPh9FG4XhbbURs0HmCbdug.htmljoin
How to write a problem statement and use the fishbone cause and effect diagram
Переглядів 5215 місяців тому
You can help solve your problems with a well formed problem statement and a root cause analysis using the fishbone diagram technique also known as the Ishikawa diagram. If you're using agile or lean with frameworks like scrum or kanban don't overlook these tried and tested techniques. So whether you're a Scrum Master an Agile Coach a Product Owner or a business analyst check this video out to s...
Fix your problems with the Theory of Constraints
Переглядів 5836 місяців тому
If you're in a bit of a mess at work then the Theory of Constraints is a great way to help you navigate and find the solution through all the noise. This video shows you how to use this simple technique to great effect. For consultancy work please contact me at Stephen.Angood@SPA-Agile-Consulting.co.uk Join my channel through memberships to get access to perks: ua-cam.com/channels/vPh9FG4XhbbUR...
Story Points Estimation in Scrum - JUST STOP! - There is a BETTER way
Переглядів 3,3 тис.6 місяців тому
Using story points, velocity and burndown charts for estimation, tracking and performance in Scrum is an outdated concept and has never been part of Scrum or the Scrum Guide. It leads to many bad habits and anti patterns and you should stop wasting yours, the teams and management’s time and drop them completely. There is a much better way and this video discusses that For consultancy work pleas...
I smell a RAT with MVP Minimum Viable Product
Переглядів 7516 місяців тому
Minimum Viable Product MVP has been around for a long time but there is a new kid on the block Riskiest Assumptions Tests or RATs. So, which should you adopt for product development? This video discusses your options. For consultancy work please contact me at Stephen.Angood@SPA-Agile-Consulting.co.uk Join my channel through memberships to get access to perks: ua-cam.com/channels/vPh9FG4XhbbURs0...
The number one skill needed for scrum masters and agile coaches
Переглядів 60 тис.6 місяців тому
This video discusses the most important and valuable skill needed for scrum masters and agile coaches both in order to get hired employed and to be sure of keeping your current role in the difficult economic environment we all find ourselves in. I tell you what you need to do and how to do it. For consultancy work please contact me at Stephen.Angood@SPA-Agile-Consulting.co.uk Join my channel th...
The BIG problem with OKRs objectives and key results
Переглядів 5137 місяців тому
This video discusses objectives and key results OKRs and how they can help organisations but also highlights their major floor and what you can do about it by using EBM evidence based management to get a more balanced and complete picture of how your people and business are doing. For consultancy work please contact me at Stephen.Angood@SPA-Agile-Consulting.co.uk Join my channel through members...
Design Thinking will help you solve your biggest problem
Переглядів 4647 місяців тому
Design Thinking will help you solve your biggest problem
Top 20 Scrum myths, which ones are you doing?
Переглядів 6597 місяців тому
Top 20 Scrum myths, which ones are you doing?
Mastering better relationships - The Newton Way
Переглядів 3747 місяців тому
Mastering better relationships - The Newton Way
How to start with Flow Metrics using Cycle Time
Переглядів 1,8 тис.7 місяців тому
How to start with Flow Metrics using Cycle Time
Agile is pointless UNLESS you do this!
Переглядів 4668 місяців тому
Agile is pointless UNLESS you do this!
The ONLY metric that counts Work Item Age!
Переглядів 5578 місяців тому
The ONLY metric that counts Work Item Age!
No Sprint Goal? You're NOT doing Scrum!
Переглядів 3428 місяців тому
No Sprint Goal? You're NOT doing Scrum!
Be original don't just follow a manifesto or guide
Переглядів 5169 місяців тому
Be original don't just follow a manifesto or guide
What is active listening? Master the art of active listening
Переглядів 5159 місяців тому
What is active listening? Master the art of active listening
If you can’t get a Scrum Master role then do this!
Переглядів 1 тис.10 місяців тому
If you can’t get a Scrum Master role then do this!
Hi Steve. Thank you very much for your videos and this one in particular. EazyBI approach is my option, but I've got stuck a bit following your steps, and I'd like to share my experience of retrieving the stories from Jira. When in EazyBi report you're specifying a "Transiton" type "In Rogress=>Done" it will work only in case of direct transition from In Progress to Done. If there're intermediate states like "In Review","In QA", etc it won't work. So, to avoid this I had to fetch all the transition statuses of stories filtererd by Status = Done, and remove the redundant transition columns already in Excel. Hope it will help to somebody.
Thank you 🙏👍 and thanks for the great tip 👍
Thank your sharing! But how to remove handoffs?
Hi, well the first step is to identify them, then depending on what they are work to remove them. For example, if the handoff (sometimes called a queue) is that you are waiting for stakeholder feedback or waiting for a committee to make a decision or sign off then make this visible and explain the consequences i.e. it causes a delay resulting in longer cycle times. If it’s busy stakeholders then work to improve the relationship. There is no one answer to how to remove a handoff it all depends on what the handoff is but identifying it, making it visible along with the consequences is your first step.
@@TheAgileLeanGardener thank you so much for your answer!
You are very welcome 🙏👍
Hello again Steve. Are there any negatives of using the sprint throughput (# of tickets completed in a given sprint) instead of the daily throughput for your MCS? I have 16 sprints worth of data and when I run the daily throughput MCS I get 6 tickets at the 85%. When I use the sprint level throughput I get 14 tickets at the 85%. Thoughts on this approach?
Hi, I’m not quite sure what you mean. To use MCS all you need for your 16 sprints is the throughput for your completed stories. So, on what date was each story completed. You then plot this on your date range in the Excel. Let’s say the first date that you had a completed story was 1st March 2024 and the last date you had a completed story was 31st July 2024. You then plot that date range in the Excel (every date in this range must be plotted whether you completed a story on that date or not) you then simply put how many stories where completed on a date, it could be 2, 5, 10 or it could be zero. Once you’ve done this you can change the date range to start in the future if you wish so long as every date in this new range is plotted. Just don’t change the column that shows how many stories were done. Are you doing this? Or have I misunderstood your question?
@@TheAgileLeanGardener I modified your template and instead of have each day listed in column A of Sheet1, I have the start date of each of my next 16 sprints listed in column A. I then put the total count of tickets from each of my 16 sprints in column B. I then changed the value in F6 (Date to Complete By) to coincide with the date value in the first Date Range column (A3).
…further thought. Usually the more data you have the better the forecast will be. The less data you have the worse the forecast will be. But the data you use must model what is currently happening. Significant changes in the team or major events (everyone is on holiday or has covid) will affect the forecast. MCS models past performance and so will forecast accordingly. So you need to use data that reflects current reality.
This won’t work. Each day in the date range must be listed, it’s very important!
The 2 templates I have work but if you change any logic they will not work, you’ve changed 2 very important things in order for MCS to work correctly. I would recommend using them as they are and see what result you get and if that closer aligns to what you’re seeing on the ground.
Thanks for the reply Steve. We do start counting cycle time when the tickets gets moved to In Progress. Our cycle times are high, but because we are completing a fairly high percentage of the committed tickets during the 2 week sprints the dev managers are not willing to take the extra time to break the tickets into smaller pieces.
Hmm I see. But the figures don’t seem to tally to me, something isn’t quite right. Are you sure the devs are moving their tickets into done on the right day? If they don’t, even a day or 2 late will skew the forecast and cycle time.
@@TheAgileLeanGardener we will look to hone that some more, but regardless, MCS is still showing only 6-7 tickets per sprint and I know we are hitting 12-17 per sprint . I know having a large number of tickets completing the last day of the sprint hurts the predictability; however, when there is a seven month pattern happening you would think it would take that pattern into account.
Yep I get it but these figures don’t tally to me, I still think something is wrong. Monte Carlo is simply a calculation based on the data input, there is no intelligence at work. Have you tried sampling a shorter more recent data sample, for example the last 8 sprints (and check the throughput for each of those 8 sprints)? Have they been any changes of significance to the team in the last 6 months?
@@TheAgileLeanGardener now I am really worried. I ran the same data through your Excel template and it shows 15 tickets at the 85th percentile. I am using ActionableAgile and it shows 6 days with the exact same data set.
Hmm the plot thickens….. Well 15 sounds more like it based on your figures.. But I’m not sure why AA is saying 6…. When I’ve compared my Excel to AA it’s always the same +-1 sometimes 2
Steve, I love your videos and I am working to move all of my Scrum Teams over to the way of Flow Metrics, but I am having an issue with explaining why the MonteCarlo simulation only shows one of my team with an 85% chance of completing 6 tickets or more during a sprint, when they typically complete between 12-17 tickets per sprint. As you can possibly imagine, their Throughput is fairly consistent; however, they are delivering the large majority of their tickets on the final day of the sprint. Even after 7 months of data, the MonteCarlo simulation has not seen this pattern and adjusted accordingly. Any thoughts on how I can overcome this hurdle in making the move? btw, the team's cycle time is 14 days (85th percentile).
Hi and thanks 🙏👍 are you doing 2 week sprints? If so your 85th percentile cycle time of 14 days is too high - but this ‘could’ be due to other factors than it actually taking that long. For example, are the team really updating tickets when the item is done on the right day? If not this will make a difference both to your cycle time and the Monte Carlo forecast. Also when does your cycle time start? It needs to start only when you move a ticket in sprint from ‘to do’ to ‘in progress’ (or equivalent). If your cycle time starts as soon as you put something into sprint regardless of whether you’ve actually started work on it then this will also skew both cycle time and Monte Carlo. I would look into this because if Monte Carlo is saying you can only get 4 or 5 items done to the 85th percentile and your 85th percentile cycle time is saying 14 days but you always seem to get a throughput in sprint of 7 or 8 then something is definitely not right.
I love the fact that I had to look up what OKR and EBM stood for. Our OKR is to reduce costs 10%. All you managers who are onboard, raise your hands! You all just got 20% pay cuts. Done!
🤣🤣🤣
Thanks. That was a great little clip. Do you mean tracking the cycle time, 85 percentile every day etc? Or do you mean on a sprint by sprint basis? You didn't mention work item age. Also, what do you mean by "building relationships"? Cheers.
Watch this one, may answer your questions ‘What do Scrum Masters do all day? I How to be a Great Scrum Master’ ua-cam.com/video/o5V8-s7_M-Q/v-deo.html
Top job, limiting wip and reducing context switching is soooo important! 👍
Thank you 🙏👍 I agree 💯
Well explained as usual Steve 👍
Thank you 🙏👍
Excellent video!
Thanks 🙏👍
Great book 📚 suggestions
Thank you, I appreciate that 🙏👍
Wow - this video went off like a rocket. Many congratulations!
Sadly not, this is an old video that I noticed was in ‘unlisted’ for some reason so I set it to ‘public’ and weirdly UA-cam thinks it’s new but is actually 2 years old. But I appreciate your comment all the same 😊🙏👍 As I’m sure you’re very well aware we don’t tend to see these kind of views on new Agile type videos anymore 🥲
@@TheAgileLeanGardener - I wondered how you'd managed to rack up 150k views in a day!!!
Yep that would have been something but no. Most of the agile channels out there are slowing down in terms of content as the views simply aren’t there, of course it does depend on why you’re doing it but if it’s purely for views then we’re just not going to get them. I’m still going to produce content but not every week, only when I have something to say that I think is useful.
But worid is full of such opportunities and anti patterns 😢
Unfortunately yes 👍
Please make a video on EBM
Thanks for the suggestion 🙏👍
Excellent.Is there a complete Kanban video please?
Thanks 🙏👍 No not yet, work in progress 🤣👍
Awesome will check more on MVP and RAT
Cool 😎
Your channel is very usefull.Thanks for sharing
Thank you 🙏👍
Hi Steve , If i use this wip limit in scrum is it called scrumban or is it a myth?
Scrumban is not a myth and can work very well for lots of teams. It’s a hybrid between scrum and Kanban and blends the two.
If SM need not resolve impediments, i feel the team will be overloaded.They will definitely need help. Self Management wont work always completely
The idea is that the SM helps the team to remove impediments themselves. The SM isn’t there to spoon feed the team. But that doesn’t mean the SM can’t remove impediments themselves but just be careful they don’t turn into a team admin!
Why we need to have release planning? As and when items are completed they should be released to PROD right?😊
Yep completed items should be released to prod ‘if’ needed. Not all completed items are ‘ready’ to be released from a business perspective.
Steve bringing customers to daily scrum is not always possible..Any tips to get them involved?
Yep speak to your product owner and explain the importance and get them to make this happen as it’s part of what they should be enabling.
Even cycle time and other flow metrics - This also depends in complexity, volume of work and risk associated..In every sprint stories differs..How the flow metrics can help for better forecasting?
It’s all about Monte Carlo Simulation for forecasting. Check out my videos on that for more info.
Very usefull . Thank you
You’re most welcome 🙏👍
I hope plugins are there for free trial
Yeah I think they all have a free trial 👍
What if a team does not have a sprint goal in one or two sprints (after so many sprints when the product is in maintenance or in matured phase)? Like there are many defects , Technical debts and each developer picked each item and no common sprint goal ? Still do they need to collaborate for defect and tech debt fixes ? And in this case what do we need to show in the Sprint review ? Kindly clarify
Scrum is designed around having a product goal and a sprint goal derived from this. If you don’t have this because there simply isn’t one I would argue that Scrum is not the right framework for you. Better off with Kanban. The Sprint Review is not intended for a ‘demo’. It is to show progress towards the product goal and to collect feedback against the completed sprint goal that may go into the backlog. I guess in your situation you could update stakeholders on the number of support tickets closed and fixes made. I’m unsure of why you wouldn’t be working on a sprint goal in each sprint though.
@@TheAgileLeanGardener Not always we work without sprint goal. sometimes there will not be features and team will pick up defects,tech debts..Have seen this in between sprints sometimes..
How does Agile provide budget and schedule certainty? Business is the art of investing money to earn more money. This requires schedules and budgets to get the green light. The "no specification" Agile with unlimited feedback loops does not provide budget or schedule certainty. Fixed length sprints are a start on schedule. They transfer schedule risk form managers to developers. Get 'er done. Burn down charts are also a scheduling device. If it weren't for that pesky customer feedback that can introduce new tasks. I worked with accountants, and it turns out every accountant has a different idea of the standard way to do anything. Often based on their specific experience (Apple or Android?). If your "typical accountant" that you rely on for feedback isn't typical, things will not go well when you sell to a broad audience. CEOs and stockholders are completely aligned with CEO stock options. They both make money when the stock price goes up. Maybe developers need equity in the software they write. That would get them to minimize cost and schedule and maximize customer value. They want as much money as soon as possible with minimal sustaining costs. Of course, management will decide that they can work just as well on low, fixed salaries as equity participation.
It's for tracking..Not to miss or.lose the sprint goal..
👍
Very true
👍
Hello agile gardener, little bit of advice! We use t shirt sizing to understand as a team the size of something relative to each user story / task and use cycle time to see how we’re performing during the iteration. In the retro we scrutinise whether something really was a small or medium using cycle time, and map out common reasons for wait times / bottlenecks. What’s your take on that approach?
As long as you’re not spending much time on t-shirt sizing and using it as a quick comparison then it sounds fine to me. You don’t mention taking a percentile against all previous completed stories (such as the 85th percentile) on your cycle times. If you’re not doing this then I’d highly suggest that you do. This will tell you how long it’s taking to complete a story, regardless of size and complexity, 85% of the time. If you’re happy with the resulting number then you’re in good shape, if not then you should look into the reasons why it’s too high 👍
@@TheAgileLeanGardener thanks so much, great to have some validation and I will certainly be observing the 85% percentile/confidence interval stuff in my inspection events with the team! Thought I’d share, but since doing what I’ve mentioned (much from watching your vids for the last few years!), it’s really made it transparent the effort required from my cross functional team to achieve the outcomes we want, and allowed us to understand what we all go through to get something to ‘live’!
@@MichaelKeywood Thank you so much I really appreciate that and thanks for all the support, it’s great to hear people getting value out of my content 🙏👍
Liked the funny and movie clippings inbetween throughout the videos 😊
Thank you 🙏👍
Whats the problem if we use XP practises like pair programming,TDD?
No problem with them at all, they are good practices 👍
Since velocity is not a good choice for forecasting,Can we use throughput, cycle time for forecasting??.They can also vary in agile world due to uncertainties ??
Throughout is what you need to forecast with Monte Carlo Simulation you don’t need cycle time for that. It’s the very opposite of uncertainty, throughout is fact, it actually happened 👍
Thank you for this tutorial. I will build a MCS using this 🙏🏾🙏🏾
You’re very welcome and thank you 🙏👍 let me know how it goes..
@@TheAgileLeanGardener I'll leave another comment. Story points should not be used when talking to stakeholders and it's best to have data that supports a claim. Plus, this keeps the spirit of range estimations and sets realistic expectations with a good chance of "over delivering"
Cool 😎 thanks Brandon 👍
Just created the Monte Carlo Simulation, thank you so much for this video 🙏🏾🙏🏾
You’re welcome 🙏👍
Do we need to estimate Spikes..My understanding is No as it's an exploration work ..Also we never know how long it takes so how spikes can ne timeboxed to no of days?
No don’t bother estimating. Set the objective of the spike to something specific, nothing too big, and set aside a few days, 2 or 3 usually. At the end collectively understand what you’ve learned and decide if what you’ve learned has moved you forward. If not try to understand why and repeat.
Hi Stephen, Wat if multiple PBI are in sprint backlog -In this case,does the Sprint Goal need to include only the highest priority one as Sprint Goal ? Multiple items is a mix of new feature,Bug fixing Stories/tasks, Tech Debts or refactoring etc
So your product backlog should be a collection of things that will achieve the ‘product goal’ which is normally created by the Product Owner. The Sprint Goal is a small subset of the Product Goal that the team believe is achievable in a Sprint. So, you pick those items from the Product Backlog that fit with the Sprint Goal. But the objective of the Sprint is to achieve the single Sprint Goal so it doesn’t matter if you complete all the items picked from the Product Backlog as long as you achieve the Sprint Goal. You may also find that as you’re working on the Sprint Goal there are other things that you need to do to achieve it that weren’t on the Product Backlog and that is also completely fine. If everything you needed to do was already on the Product Backlog that would virtually be waterfall.
@@TheAgileLeanGardener Thankyou I did not understand last line.Yes all items will be in product backlog,how this is mini waterfall
Yep mini waterfall. Because if you create all the stories upfront that’s exactly what happens in waterfall, requirements definition phase. So many teams / organisations use Scrum but are actually doing mini waterfall, not just because they create all the stories upfront but because they don’t have releasable value at the end of each sprint. The idea of user stories comes from XP and the point was all about card, conversation and confirmation. So it’s basically a note to remind you have that conversation in sprint and work with stakeholders, customers etc to understand what they need and do this continually throughout the sprint, not at the end e.g. sprint review. Without this you lose creativity, innovation and adaptability.
@@TheAgileLeanGardener In waterfall the requirements are fixed.But in scrum the backlog keeps evolving/refined ..
Thanks for this..i was looking for an one to get rid of story points..Its a new learning
Thank you 🙏👍
I dont see the link to exvel sheet
It’s in the description towards the bottom…
@@TheAgileLeanGardenerThank you overlooked it
Amazing one
Thanks 🙏👍
I recently discovered your videos and it's been nothing short of ACE! ... Question: How do you move on to the next phase of using the Monte Carlo method of forecasting with the data gathered here seeing that one important data missing is "the number of items completed per date"
Hey and thank you so much, I really appreciate that 🙏👍 Check these two videos out for how to actually do Monte Carlo Sim: MCS How many by when ua-cam.com/video/k22ZwODjgkE/v-deo.htmlsi=8TZhpN4xpTtHo4wQ MCS When can I get x number done by ua-cam.com/video/hQOs5CfkOJU/v-deo.htmlsi=swodpH3DJyxRe3ox
Great video!
Thank you 🙏👍
I feel like scrum master should be a virtual role and stop being a job title.
Yeah there is a good argument for that, it’s an accountability not a job title 👍
Leadership is at fault, middle mgmt is worse. The team is adaptable but organizations think servant leadership starts and ends with the scrum master 😵💫🙄
🤣🤣🤣
@rommelbandeira after creating the automation the custom fields updates fine when the status is "In Progress". If I change the status back to "To do", is it possible to clear the CT start date field to show as empty or no value in it?
Hi, well to do that you’d have to create another Jira automation rule to clear the CT Start custom field if an item transitioned from In Progress to To Do. But I’ve set it the way I have done so that it’s less easy to ‘game’ the system. If an item moves from To Do to In Progress then the cycle time has started so you shouldn’t reset it. I assume you mean if it’s done by mistake. Alternatively you could get the Jira admin to reset the CT Start custom field, it’s a bit more hassle but you could make it the job of whoever moved an item by mistake to In Progress to get this sorted to try and discourage these mistakes and to take more care.
@rommelbandeira Will it work for "Team-Managed" project template?
Hi, that’s a good question and I’m not sure. This was done on a company managed project template but give it a go and see 👍
@@TheAgileLeanGardener It does not work as you have showed in this video for Team managed project template but at one step when you have to associate an issue operation with a screen in teams template, we have to go to settings > issues > screen schemes > associate an issue operation with a screen
Ok thanks for the update and info 🙏👍
Hi Steve, if my team's cycle time (CT) is very inconsistent (very different from one to the next) for the last 6 months and I'd like to use MC simulation, what do you suggest I should do first?
Hi, my suggestion on this is always the same. Get the cycle time under control first. For example, if you’re doing 2 week sprints, you want (as a minimum) your 85th percentile cycle time for all completed stories to be 10 days or less. Ideally it wants to be less than that, 5 days or less. If you find that it’s something like 15 days you need to look into the reasons for this. It could be stories are too big, you hadn’t identified dependencies or constraints, there are some handoffs in your process (such as waiting for stakeholders or committees etc). If you don’t get your 85th percentile cycle time under control before using Monte Carlo it’s likely that your forecasts won’t be realistic.
@@TheAgileLeanGardener Great explanation, thanks!
Great! I need to watch this again though 😁 thank you Steve
You are very welcome 🙏👍
Great video, thanks! If I'm using KFM (Kanban Flow Metrics) with scrum, how can I track progress of the team in a s sprint in Jira - what chart(s) in Jira can I use? Thanks
Personally I would concentrate on the sprint goal (assuming you have a product goal). Jira doesn’t have any decent charts, I wouldn’t bother with them. This is why I created the ageing wip Excel and the Monte Carlo Excel, using these you can do it for free. The trick is getting the data out of Jira - you can do this for free for cycle time/throughput by following my recent ‘extract data from Jira’ video but to get the data for the ageing wip chart you’ll need a plugin like Time in Status (you can also do it with Jira automation but it’s a little trickier). Or you could just spend the money and buy the ActionableAgile plugin that gives you everything.
@@TheAgileLeanGardener Fantastic, thanks
Excellent, as always - thanks
Thank you, really appreciate your support 🙏👍