Scrum and Stacey diagram for Scrum Master

[@priyakmdi]

Stacey diagram and the applicability of scrum were the key takeaways - explained very well

[@arupdasgupta5589]

Key Takeaway- Got absolute clarity on the set of actions, team and responsibilities associated with Sprint

[@mamtagarg3875]

This video tells us the concepts of scrum, it’s various events, activities that happen in each event, advantages of inspect & adapt, Stacey diagram & where is scrum best suited. Great video which gives clears the concepts.

[@TheTruthseeker369]

This video explains SCRUM concepts. However the use of Stacey Diagram has made it really easy to understand the significance of SCRUM in complex zone. The presenter has really made it simple and easy to understand.

[@meghabhargavawarman3091]

To know the essence of Scrum, we need to Inspect and Adapt at regular intervals , usually small, to reduce the cost and Risk while working on a workable Product. very well explained.

[@meandean4446]

A very good segway into the Stacey Diagram with clear separation of different types of project/product environments and challenges.

[@xenababoon]

Great elaboration of scrum and stacey diagram. The core of scrum is Inspect and Adapt!

[@divya733]

I/A is a very important concept n scrum. Stacey Diagram explained very well.

[@cherryannbuenaflor5844]

- Inspect and adapt is a core aspet of the scrum. Very well said! - Sprint is Inspect and Adapt. [cherry]

[@NaveenNanjundappa]

Everything revolve around I/A

[@dipikasinha5700]

Great video on understanding scrum events it's order and importance.

[@TheWanderingPrince]

Another great video that articulates the importance of Inspect and Adapt and how it is integrated in the entire Scrum framework. Also the Stacey Diagram that helps identifying when to use the Scrum and when not to.

[@savithavijayan8604]

Helps in understanding the mistakes that we are doing in scrum process and helps in correcting them. It also articulates the importance of frequent inspect and adapt which in turn helps in reducing the risk

[@SHALINISINGH-ow3zw]

very visual and detailed way of explaining the concepts, thank you so much Naveen!

[@skhadse]

Key Takeaway : Nicely explained scrum events and sprint details. Importance of Inspect and Adapt frequently at every step. Stacey Diagram to understand complicated and complex zone.

[@subarnakhatri6245]

Really meaningful video explaining how scrum is useful in complex and complicated zones, and how continuous inspection/adapt helps in such situations.

[@seshuvutukuri6450]

Inspect and Adapt is core of scrum that can lead to improved techniques which is critical to success of product increment. Nicely explained

[@NaveenNanjundappa]

Thanks for your kind words and your takeaway is right

[@samuelraja3689]

Nice video with stacey chart explanation, very useful to know its underlying things.

[@PankajSingh-rs7zj]

good detailing on SPRINT RETROSPECTIVE and various situations defining certainly and uncertainty in Project and Product lifecycle

[@user-qv7to3pc3v]

A complete and precise review of scrum framework

[@rajivnayanverma6822]

Nice explanation on the Stacey Diagram . Understood that scrum will be helpful in the complex situations.

[@NaveenNanjundappa]

Glad it was helpful!

[@sankhyachattopadhyay2158]

Hi Naveen, thanks for explaining the scrum events in such finite detail. I/A(Inspect and Adapt) with small + reduce risk + Reduce cost of the fix is the core fundamental to ponder on.

[@dominic1969]

the series of sprints illustrated @11:25 was something i had struggled a lot to understand when I started with Scrum .... wish I had done this CSPO years ago !

[@NaveenNanjundappa]

thank you so much, I wish you had done this years ago. better late than never :)

[@bownki]

Stacey diagram is something new I have learnt, and how Scrum can be used to navigate through the uncertain situations.

[@1901rajan]

1.Sprint is fixed time, regular cadence, breaking down the requirement in small i/a items, build prod , review and retrospect event series. 2.Sprint is independent of release cycle. 3.Best suited in complex zone.

[@Gaurav-uv3vy]

At the core of scrum (which is the only framework that works in a complex zone where requirements and technology are both fairly uncertain) is the iterative Inspect and Adapt cycle. Scrum is empirical in nature which is why it is best suited to developing solutions in a complex zone.

[@vincenzoaltimari7320]

from the video is clear why scum is best suited for complex zone where you need to inspect and adapt to what you found. It's simply because scum itself it's a framework based on different type of inspection and adaption loop (for product, for tools, techniques etc). Well said

[@NaveenNanjundappa]

Yes. Use scrum when you need to inspect and adapt

[@PankajSingh-rs7zj]

Empirical thinking is key to success

[@jakobsch8377]

Scrum and its sprints as an iterative framework to inspect and adapt to improve on a rolling basis; identification of the complex zone using the stacey diagram and benefits of scrum in complex projects

[@lotfial-sarori7385]

Key Learning for me from this video:Scrum is most suitable for complex zones where requirements are uncertain and technology is uncertain. Highly uncertain requirements with highly uncertain technology is chaos where nothing works so you will need to fix that high uncertainty while for certain requirements with certain technology, any known methodology would work even Waterfall. Sprints are time frames in Scrum. Spring Planning (8 hours max) involves setting the objective and how (the Plan). Daily Scrum (max 15 minutes) to inspect and adapt the strategy during product development (the How). At the conclusion of a Spring, we have Product Review (4 hours max) to inspect and adapt the Product Increment to make sure it is usable and done, and Product Retrospective (3 hours max) to inspect and adapt collaboration, process, tools, techniques, and strategy. Scrum is most suitable for complex zones where requirements are uncertain and technology is uncertain. Highly uncertain requirements with highly uncertain technology is chaos where nothing works so you will need to fix that high uncertainty while for certain requirements with certain technology, any known methodology would work even Waterfall.

[@bornalisingh5847]

The key takeaway for me from this tutorial is understanding the importance of inspect and adapt in scrum framework. I/A is the core of scrum. Also, sprint is a loop to inspect and adapt and the scrum events are opportunities for team to I/A. You explained it beautifully sir.

[@NaveenNanjundappa]

Awesome, I'm glad you are able to see the importance of inspection and adaptation to be successful in complex systems

[@utkarsh1091]

The importance of breaking or refining the backlog is always ignored, this video helps is avoiding that mistake.

[@affannafees7147]

Key takeaway is that continuous improvement can be achieved by inspect and adapt. Understanding the stacey diagram was definitely beneficial.

[@priyankahangloo7157]

KeyPoints: I/A(Inspect and Adapt) with reduce risk + Reduce cost of the fix+ keeping it small in the complex zone is the core fundamental point to always consider with scrum framework.

[@ashishwrite8022]

Hi Naveen, Key takeaways for me is 1. Scrum as Inspect & Adapt + Small + Reduce Risk + Reduce Cost of Risk. 2. Different Scrum Events and their relevance 3. Relevancy of Inspect & Adapt in actual environment using Stacey Diagram talking about requirement + domain certainty & uncertainty.

[@purvaverma2524]

The video talks about the Scrum and Scrum events. Each sprint can be considered as cycles of I/A. The Stacey Diagram divides the region as Simple, Chaos, Complicated and Complex zones. Simple zone - where both the requirement and technology are clear. Here any framework can be implemented. Chaos - where both the requirement and technology are clear. Here none of the framework will work. Complicated - where either requirement or technology has challenges. This requires I/A cycle. Complex Zone - where both requirement and technology are moderately uncertain. This requires I/A cycles which is done more frequently and the E/E actions are taken. In other way scrum framework is the most optimum framework which can create a winning product in complex zone.

[@ananthaj]

Sprint retro allows for inspection of tools, tech, process, strategy and people aspects to make an adaption to improve sprint goals, dod.

[@ananthaj]

Incremental changes go towards to sprint goal. Daily scrum allows for each dev to inspect and adapt towards sprint goal. PO is optional. PO feedback during sprint review can get into product backlog.

[@virendratheprince]

Backlog refinement needs involvement of stakeholders?

[@PriscillaNwachukwu-r3c]

Key Take-Away: With focus on the Stacey Diagram: The Requirement axis is what tells us about "What needs to be done", whereas the Technology axis tells us about "How it needs to be done". In a situation where both are uncertain, then it is considered as a Complex Zone, this is the kind of zone where the Scrum Framework is typically applied to. In zones like this, Inspection and Adaptation are the keys to winning.

[@Makeovertime.]

Nice video Naveen. Thank you

[@NaveenNanjundappa]

Thank you.

[@AkankshaPhapunkar]

Three key takeaways: 1)Understanding of Sprint Planning meeting and people involved and their roles 2)Inspect and Adapt is the key functionality of reaching the goal 3)Understanding on Product Backlog Management

[@mvrsrivatsava13]

Key take aways: 1. Sprint planning: identity goal. Pull sprint US. Add activities to the user stories. PO set goal. Scrum master set the plan. 2. Daily scrum: look for incremental I/A. They can keep, change or adapt the plan. 3. Sprint review: review the work by PO and stakeholders. 4. Sprint retrospective: see how they have been working.see what went well, what didn't go well and what needs improvement. Plan do check and act of inspection and adaptation throughout the empirically. Stacey diagram: Laying out requirements over domain or technology to identify how the requirements fall in which zone.

[@jignalodaya4515]

Ket takeaway is the best suited for complex zone is SCRUM through Empirical Diagram and Stacey Diagram. By following same principle of Inspect/Adopt + Frequency + Effective/Efficient Decision/Action

[@sridattavirivinti1480]

Key takeaways - Inspect and adapt at every stage of the sprint, this is the mindset required for everyone using the SCRUM framework. Different activities in scrum.

[@ruchibhatjiwale8903]

3 Key Takeaway- Scrum Framework is essentially based on the concept of Inspect and adapt at short intervals to reduce the risk/ minimize the cost of fix in a complex zone with a goal to develop a product increment (adding value to the product) with each cycle. The short time unit is called as Sprint (max 4 weeks) which is a loop of I/A The goal of sprint is to develop an incremental product with each sprint

[@AnandKulkarni-mw8rf]

Detailed explanation on Scrum and Empirical Thinking

[@priyadarshinilakshminaraya747]

Scrum is best suited for Complex Zone in Stacey Model . Scrum events are cycles of Inspect & Adapt to solve complex problems.

[@ananthaj]

Why scrum we need is answered thru Stacey diagram. When there is chaos in requirement, tech and if these needs to be managed. Scrum provides a framework which allows for us to inspect and adapt frequently and take effective and efficient actions.

[@Manoj_kumar_bana]

Thanks a lot Naveen for such a great explanation and it is really helping a lot for understanding the core concepts of scrum. I am sure you will help for other topics as well....will wait for your valuable topics over here. Once again thank you much and appreciate for your hard efforts.

[@NaveenNanjundappa]

I'm glad you found this video helpful. Thanks for your kind words

[@abrahamprasad8602]

Inspect and adapt is the main aspect of the scrum - Abu Prasad

[@NaveenNanjundappa]

you will never forget I/A in your life time :)

[@ammarhusnain170]

Key takeaway - Inspect & adapt as you progress. Scrum master helps with facilitation. P.O. is optional in daily scrum.

[@ankitjainblg]

Key takeaways - 1) In sprint planning - 3 questions need to be answered - WHY?, WHAT & HOW ? to reach the goal 2) PB - is the To do list for the sprint and the goal to achieve. Its accountability is with the Developers and they can take help from SMEs 3) I/A is done on the product in the Sprint review phase. This changes on the product increments results as a new item on the Product Backlog.

[@terkumaivue6715]

key takeaways. 1. Scrum is best suited in a complex zone and scrum is a cycle of inspect and adapts. 2. product backlog refinement is to break down larger requirements into smaller requirements. It also deals with prioritizing items in the product backlog. 3, In the complex zone, we inspect and adapt frequently and use effective and efficient actions.

[@shaliniantony5088]

Very simple to understand

[@sarthakjena2000]

3 key takeaways: 1. The sprint backlog mainly involves the developers 2. The approach evolves through the daily scrum 3. A sprint is essentially a cycle of inspecting and adapting

[@shashinshrivastava7539]

Key takeaway: Sprint is simply the unit given for the loop of inspect and adapt. This helps the scrum team in continuous improvement. Keep evaluating the increment and focusing on sprint goal.

[@ananyakar5131]

Thank u for such a simple explanation

[@NaveenNanjundappa]

thanks for your comments. I am glad you liked it.

[@ipsitaroy6242]

The core concept of scrum is to Inspect and adapt. A team can achieve a goal by considering frequent inspections and adaptation in each repetitive sprint. Scrum is useful in the complex zone in the Stacy matrix diagram.

[@AnandPatel0721]

1. Inspect and adapt in every stage of sprint 2. sprint retrospective I/A on the people, process, tool and tech 3. product backlog refinement has to happen before sprint ends 😀

[@sunainanaina2820]

Key Takeaway: Stacey Diagram was new to me. It's essential to comprehend cause and effect while decision making.

[@mattyross1285]

Latest release is 2020 - first part is spring planning meeting - defining why we are doing it, and how long we need, Product owners, review the goal and extract the product backlog and develop the plan to reach the goal. The details small goals to be achieved are called sprint backlog. The accountability of the plan is with developers. At the end of meeting, developers can define what is the goal and how they are planning to achieve it. Session would be 8 hors. Developers they run IA on daily basis to verify how they are progressing and run IA. Scrum master facilitates the developers to achieve the production, and Product owners are optional and can partake by being silent observers. Detailed planning can be discussed after daily scrum. Sprint review is to review the product produced during sprint, product backlog is developed and a risk can be included as well. Sprint retrospective, is continuous improvement for tools, people strategies, improvement items etc. action items for next sprints and required collaboration is also discussed (3 hours discussion for a month sprint) Product Backlog refinement - the scrum team review all the product backlog items if they need revision and decides if spints are manageable for next run. The product release, is irrespective of sprint cycle. Product release starategy is the decision of the product owner. Events in scrum is an opportunity for I/A. Stacey Diagram - looking at uncertainty level in technology and requirements In Scrum Product Backlog and technology is uncertain and its welcome. Scrum is cycles of inspect and Adapt

[@stephanttqqqqqqtqqqqqqqqqq5668]

3 Key takeways: - involvement of different stakeholders (developers, SMEs) in planning to clarify goals. - inspect/adapt to reach the goal - daily scrum: inspect/adapt the plan to reach the goal

[@aneeshjoy9629]

The importance of I/A is mentioned.. If I/A is not there then : 1) Sprint planning meeting is equal control and command center 2) Daily scrum is reporting structure 3) Sprint Review is Signing of the work done 4) Sprint retrospective has no improvement Scrum is best suited in complex zone where both axis is moderately uncertain

[@heriantoherianto4053]

Key takeaways is the sprint timeline and in each phase we should inspect and adapt , and then start to plan again untul the product is done. Also get more details on Stacey Diagram

[@NaveenNanjundappa]

Perfect

[@swatiseth274]

Key takeaways: 1. Scrum is used in a complex zone 2. Scrum works in cycles of inspect and adapt. 3. Frequency of sprints is fixed the scrum, team tries to achieve incremental developments, works efficiently and effectively, experiments, reduces risks and costs, improves quality - all work to achieve the desired goal

[@soumya24ks]

Key takeaway: Main events in scrum - planning, daily scrum, review and retrospective. Core action is always the I/A. Best use of scrum is with the complex zone.

[@ts-krishnan]

Takeaway/learning: (1) Stacey diagram: high certainty and high uncertainty across two axes - requirements and technology. Complex area of the diagram is where scrum is more useful. (2) More details on the elements of sprint - an appreciation of terms like product backlog, sprint backlog, daily scrum, I/A daily and at a sprint level, etc. Hoping to reframe these in the context of my prior experience during the CSPO sessions.

[@nehamathur1979]

Key takeaways: 1. Scrum is best suited in a complex zone. 2. Scrum is a continuous cycle of Inspect and Adapt. 3. As a heart beat of scrum we have Inspect and Adapt loops in the name of Sprints. 4. The frequency of Sprints are fixed.

[@AdnanZaidi-h5y]

Key Takeaways: 1. Scrum events - 4+1 (Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective + Sprint). 2. A Sprint is cycles of inspecting and adapting on the product, plan, peoples and processes - empirical process. Plan, do, check and act 3. Stacey Diagram - two axis of uncertainty, simple zone, complex zone and chaos zone.

[@carlosgutierrez972]

Congrats it was a great video. Do you have a video about the product owner?

[@NaveenNanjundappa]

Thank you. I'm glad you liked the video. Other topics shall be posted in coming days

[@deeptipeshavaria]

Key Takeaways: 1. Product owner are accountable to set goal, Developers fetch the backlog items to achieve this goal and Scrum master helps with plan to achieve the goal. 2. Daily scrum is used to inspect and adapt if they are on correct path to achieve the goal. This helps to focus on the goal. 3. Sprint review happens at the end of sprint. They review the product, I/A and take into account if there are any sprint backlogs.

[@raghavendravns]

Simple and clear.

[@NaveenNanjundappa]

thanks for your comments. I am glad you liked it.

[@gobanarasu]

Scrum is best suited when products uncertain and changes evident and tech/domain uncertain Scrum is best suited in complex zone and scrum is a cycle of inspect and adapt Frequency is fixed and moves towards achieving the product goal

[@akankshaphapunkar4732]

Three Key Takeaways- 1)Inspect and Adapt is the main functionality 2)What is sprint planning meeting and who all are involved in the process 3)Importance of Product Backlog Management

[@nigamabhishek001]

Key takeaway: Scrum events and role of I/A at every step. Good to learn about Stacey diagram - certainty vs uncertainty

[@vikaskannan3160]

Key takeaways- Understanding of different scrum events and how inspect and adapt plays a crucial role. Also how the scrum teams use the stacey model to understand their position and I/A accordingly

[@alpanachaturvedi]

3 Key takeaways are: 1) Scrum is a fixed time cycle loop of I/A 2) Scrum is best suited for a Complex zone where risk is higher , where I/A is the core of the scrum 3) Release cycle maybe different than the sprint cycle

[@rochellebyrdsong2305]

3 Takeaways: 1. Sprint planning to define goals 2. SBI to complete and inspect/adapt 2. Sprint review to inspect/adapt

[@nithinkurup3111]

Key takeaway: Scrum is most suited for complex zone (stacey diagram), and both axis (requiements and domain tech) may need frequent Inspect and Adapt cycles.

[@hnhjhaveri1125]

Inspection/Adating are key to success of the plan Frequency of a sprint in fixed, we need to achive incremental growth within each sprint Stacey Diagram -Hipul

[@williampoletto9518]

Key takeaway: scrum events are a means of inspecting and adapting continously, and scrum is best suited for complex scenarios (moderate incertainty in requirements and technology)

[@ShrutiAmritphale]

Takeaway: Sprint is cycle of inspect and adapt. Various scrum events, when to conduct them, who participates, who are accountable and what is their importance. Scrum is most useful for complex projects as it is based on empiricism.

[@sitararaman6320]

Takeaways 1. The events of scrum are sprint planning, daily scrum, sprint review, and sprint retrospective 2. Inspection and adaption is the key to succeeding in scrum 3. Scrum is best for a complex zone

[@shaikatdas7612]

Key Takeaways from this session: 1.PO sets sprint goal and SM helps scrum team to plan -- mitigations of risk, removal of dependencies & work collboratively to achieve goal 2.In sprint review , PO reviews product increment that has been built and provides feedback on changes required if any and forecast their occurences 3.Sprint Retro has an intent to look for continuous improvement 4. Stacey Diagram: Having 2 parameters in 2 axis - Requirement (what) VS Domain & TECH (how) ---> Simple zone(anything works), Complicated (Moderately uncertain) & Complex zone & Chaos zone (nothing works)

[@sandeepsrichandan8978]

Key Takeaway : Frequent Inspect and Adapt is key to the Scrum. By constantly inspecting and adapting the small incremental requirements in a shorter timeframe the team reduces the amount of Risk and Cost of Fixing and eventually reach the goal successfully.

[@rajithamarapally9184]

Sprint Planning - Why we are working on it? What is the Goal? Plan to reach the Goal? Sprint Backlog /SBL - done by Developers. Inspect and Adapting is the Core aspect of Scrum. Complex zone - both Technology & Requirements are complex - We need Scrum Framework. I/A and Frequency + E/E actions.

[@ManasaUpadhya-kp9yg]

Key Takeaways are - 1. I/A + Small Chunks + Reduce Risk + Reduce Cost of fix 2. Scrum to be applied in complex zones 3. Sprint planning to contain the Goal ( what) and Plan ( how) and to continuously I/A throughout till the end of the sprint

[@jenineross6186]

Key Takeaways: 1. Sprint is Fixed time, regular cadence & ensure small requirements to reduce risk & inspect & adapt everyday day, continued cycle 3. Plan, do, check & do, Inspect & Adapt (Core aspect of the Scrum) = continuous improvement known as Empirical Cycle 3. Stacey Diagram - Complex zone (moderate uncertainty on both Requirements & tech) - Scrum is best & requires I/A, frequency & E/E actions

[@sahanagangal9814]

The core aspect of Scrum is to continuously inspect and adapt. It is used in complex zone.

[@catherinemarymathew8141]

Gained insight on how relevant inspect/adapt cycle is for scrum events

[@AmanpreetSingh-ru2nm]

Key takeaway: Continuously inspecting and adapting is the essence and core of the Scrum methodology.

[@curvirao7059]

Key Takeaways - 1. Sprint is an Inspect & Adapt loop 2. Scrum Events are opportunities for the team to Inspect & Adapt 3. Scrum is best suited in a complex zone where requirements and technology are moderaly uncertain and require frequent I&A cycles to take effective and efficient decisions

[@ShubhangiBansal-p5c]

3 key takeaways: incremental changes are adaptable goals done in daily scrum, inspecting and adapting is important for scrum and making decisions as per priorities in the review of sprint, Small chunks in scrum can reduce risks and Stacey's diagram helps in decision making in businesses.

[@zo7588]

-Accountability of the plan is with the developers - In a winning team, they are always inspecting/adapting, and coming up with a strategy - Scrum team consists of: Owner of the product, scrum master and developers

[@venkyjoshi1488]

Understanding the importance of inspect and adapt in scrum framework. I/A is the core of scrum. Also, sprints is nothing but to inspect and adapt. Scrum events are opportunities for scrum team to I/A.

[@RaghulPatteri]

- Empirical cycle - Plan - do - check - Inspect&Adapt and act

[@corinaioanamicu]

Below are my 4 key takeaways, after watching Naveen's video on Scrum and Stacey diagram: 1. During Sprint Planning: - The accountability of the sprint plan sits with the developers; - The Product Owner sets the goal, while developers Inspect & Adapt toward the goal; - The Scrum Master helps the team plan effectively by reminding them about the risks, dependencies, and design and making sure the team works collaboratively; 2. During the Daily: - The developers look at the plan and change it if necessary, so the sprint goal is achieved; - The Scrum Master facilitates the meeting and helps the team to be efficient and effective; - The Product Owner is optional in terms of participation, but should they choose to participate they will be silent observers; 3. During the Retro meeting: - This is a meeting that focuses on continuous improvement in terms of people, tools & techniques, processes, and strategy; - It happens on the last day of the sprint; - Possible results of the retrospective are: changed DOD (definition of done), improved processes, new T&T (tools and techniques) to try; 4. The Stacey diagram: - It has 2 axes, the requirements one and the technology one; - Each axis starts from highly certain to highly uncertain; - A simple project sits in the area where requirements and technology are certain; - A complicated project sits in the area where requirements or technology are uncertain; - A complex project sits in an area where requirements and technology are moderately uncertain; - Scrum framework works best for complex projects, as it encourages frequent inspection and adaptation;

[@proudkislaya]

Three Key Takeaways a) Purpose of Scrum is to inspect and Adapt in the name of sprints. b) Sprint cycle is completely independent of the release cycle c) As per the Stacey diagram, 4 different types of projects are available Simple/Complicated/Complex and Chaos. Out of these 4 Scrum works best for Complex models

[@GouriTripathi-fk3pk]

The key takeaways: 1) Sprints are inspect and adapt cycles, of small duration, to keep the risks small. 2) sprint planning without I/A leads to plan driven development, daily scrum with out I/A is a status update, sprint review without I/A is sign-off for the product worked upon, sprint retrospect without I/A is no improvement on tools and processes. 3) S/w development being a complex zone problem, scrum as a framework is best suited for managing it.

[@annjose324]

Key takeaway: Scrum events and role of I/A at every step. Inspect and adapt is key for Scrum.