Sprint Retrospectives - Continuous Improvement Mindset by Naveen Nanjundappa

[@pritidr10]

The idea of continuous improvement or Kaizen has always been emphasized and this video explains the agile concept well.

[@rvtejas1]

Key Takeaways are the SR enables the team to improve continuously and discuss on the strategies , tools and techniques, process , relationship and make the necessary changes during these meetings.

[@heriantoherianto4053]

Key takeaways are the details of sprint retrospective: the definition, the purpose, and what kind of things that should be discussed in this sprint, such as people, process, relationship, tools, and so on. good explanation sir

[@NaveenNanjundappa]

It's continuous improvement..

[@shaliniantony5088]

Gives a clear picture on the continuous improvement mindset

[@vincenzoaltimari7320]

I think this video can be very useful as a Scrum Master to explain to the team member why this event is so important and should be always attended with the right mindset

[@bornalisingh5847]

Very well explained Sir. As a team we should have a thought process of continuous improvement. As a Scrum Master we should educate the team to understand the importance of retrospect meeting and that its for team's improvement.

[@NaveenNanjundappa]

Absolutely. you are right.

[@mattyross1285]

Learn from mistakes. Do result, analyze, infer, plan and then do - Emprical cycle - PDCA or Ispection and adaptation. The sprint retrospective is an opportunity to obtain the improvements thoughts right before the sprint end and discuss in a session with the project team members.

[@snehitajain7609]

Key takeaways: 1. Empirisum 2 focus on continuous improvement 3 and very useful as a scrum master to explain all the aspects to the team members why this event is so important and why we need to attend it always .

[@divya733]

We always have to take away improvements and plan on implementing them for the next sprint.

[@mamtagarg3875]

Mindset required & usefulness of sprint retrospective

[@abyarora]

Thanks for explaining the concepts. What are your views on adding some fun element to the retrospective meetings?

[@NaveenNanjundappa]

Ofcourse

[@vikaskannan3160]

Key takeaway- Retrospective is a platform where the team gets together and discusses how to improve the process, people relationship and the likes. This is where models like Empirical cycle can be used.

[@dominic1969]

the little historical aspect of restrospectives is helpful when discussing scrum with newbies - the "why" of retros

[@NaveenNanjundappa]

Absolutely, when there are new members it's important to explain why we do what we do...

[@ts-krishnan]

Takeaway/learning: (1) Why was Sprint Retrospective included? It was not there initially. (2) Core purpose of retrospective - to focus on continuous improvement of people/process. (3) Important to have the right mindset while entering the retrospective meeting - we will improve by delta after the meeting.

[@sunainanaina2820]

Key Takeaways: Retrospective events reinforces team work positively and encourages continuous improvement.

[@venkyjoshi1488]

As a Scrum Master we should educate the team to understand the importance of retrospect meeting and that its for team's improvement. Sprint Retro enables the team to improve continuously and discuss on the strategies , tools and techniques, process , relationship and make the necessary changes during these meetings.

[@soumya24ks]

Key Takeaway: Even with the focus on I/A on a daily basis, it's efficient to do a complete review with the main aim of ensuring E/E actions are taken as part of the improvement. This mindset will help in delivering better further.

[@ankitjainblg]

Takeaways - Sprint retrospective is based on Empirical cycles which involves - Do- See Results - ANALYSE - INFER- PLAN & DO in a cyclic manner Goal of Sprint Retrospective is to do Continuous Improvement Sprint Retrospective is mainly done on T/T, Strategies, People , Management, Processes

[@subarnakhatri6245]

A sprint retrospective is also a part of the sprint and helps in inspection and adaption in terms of people, relationships, tools, and processes for continuous improvement.

[@ipsitaroy6242]

The sprint retrospective is the step for continuous improvement of technology, process, people, strategies, Management, and relationships.

[@mohitgupta4489]

Key Takeaways 1. Retrospective meetings (sprint retrospectives) are an important tool for continuous improvement in teams. 2. These meetings allow the team to discuss and evaluate what went well, what could have been done better, and what went wrong during the previous sprint. 3. The focus is on inspection and adaptation, using models such as the PLAN-DO-CHECK-ACT (PDCA) cycle, to improve processes, people relationships, and other areas. 4. The retrospective meeting is an opportunity for transparency and collaboration among the sprint team, and for the Scrum Master, team members, and manager to play their roles in driving continuous improvement. 5. It is important to have a mindset of continuous improvement and to schedule specific time for it in the form of sprint retrospectives.

[@shashinshrivastava7539]

Key takeaway: Sprint retrospective contributes in evaluation of 'What went well', 'What could have been done better' and 'What went wrong'. Also team should always inspect and adapt, focuses on continuous improvement.

[@catherinemarymathew8141]

Got a detailed insight on importance of sprint retro

[@meandean4446]

Key takeaway : 'Get better' is only possible with a reflective mindset, clearly inspecting and adapting and ensuring changes are made to strategy based on the outcome of the retrospective.

[@ammarhusnain170]

Goal of sprint retro is continuous improvement.

[@sarthakjena2000]

3 key takeaways: 1. Retrospective facilitates analysis of the sprint 2. Retrospective provides the points of improvement for the team 3. Major improvements are around the people, tools, strategies and management

[@efrelyndavid3729]

Sprint restrospective cater the continuous improvement of the team. Continuous improvement is everyone's responsibility.

[@TheWanderingPrince]

Key Takeaway: The importance of continuous improvement and scheduling specific time for it in the form of Sprint Retrospective. In this meeting any of the following may be discussed: tools,techniques, strategies, people, relationships, process, management, culture etc.

[@yeschandana]

Key takeaway: Sprint retrospectives allow the team to learn and improve (inspect and adapt) in order to achieve higher effectiveness and high-quality results through strategies, tools and techniques, processes, and relationships. Sprint retrospectives improve the team, and sprint review enhances the product.

[@alpanachaturvedi]

3 Key Takeaways on Retrospective: 1) Focus on Continuous improvement 2) Could be everyday or once at the end of the sprint 3) Complete transparency and involvement of the whole scrum team is required

[@lavanyamanjunath634]

Key Takeaway: > Why Sprint Retrospective is important > Importance of continuous improvement > This meeting can be used to discuss - what went well, what went wrong, Ideas of the team members, People issues, Process issues etc

[@DeepakShivnani]

Key Takeaways 1. Sprint retrospective is to have discipline to do review at the end of sprint and do continuous improvement 2. Plan Do Check ACT and Inspection and Adaptation are other ways of doing continuous improvement 3. Out of every Sprint retrospective meeting we should come with some learnings and focus should be on continuous improvements.

[@ShubhangiBansal-p5c]

3 takeaways: 1) Understand the srpint mistakes is very important. 2) Space of no judgement and openness in the communication for the most effective retrospection and open collaboration should be promoted. 3) Restrospection's main goal is the hope of continuous improvement.

[@abrahamprasad8602]

Continuous improvement for a better team, tools/techniques, strategies and relationship. - Abu Prasad

[@NaveenNanjundappa]

yes team should feel, we are better today than yesterday...

[@bownki]

Retrospective from what I have seen have changed from talking to just typing. There are three options to select from. 1. What should we continue to do? 2. What should we stop doing? 3. What new things should be done?

[@nithinkurup3111]

Key Takeaway :During retrospective meeting, promote transparency and collabration among the sprint team- which will lead to continous improvement

[@SHALINISINGH-ow3zw]

my key take away on Sprint Retrospective is first its a process of continuous improvement within am organization, within a sprint or at the end for an Effective and Efficient utilization of resources and skills. They can be conducted either in a closed room considering if team members are not able to open up on issues or even anywhere in open or comfortable location depending if all the team members have the same goal of bringing Effective and Efficient utilization of processes and resources. In a way a SR contributes to an effective and Efficient planning and execution of a project.

[@terkumaivue6715]

Key takeaways 1. the sprint retrospective is to inspect and adapt on people, tools, techniques etc. for continuous improvement. 2. Promotes transparency within the team 3. comes at the end of the sprint

[@GouriTripathi-fk3pk]

Key Takeaways: 1) Scrum team should meet at the end of sprint for retrospective, in order to inspect upon how things are progressing , related to people, process, tools, techniques, strategies, culture, and figure out areas of continuous improvement. 2) Scrum masters should make the team aware of why it is necessary for team to undergo continuous improvement. 3) Managers should encourage the team to collaborate to come up with pointers for continuous improvement.

[@vksomething]

Very well presented

[@NaveenNanjundappa]

Glad you liked it

[@nikkiayeni2790]

takeaway: continuous improvement is the driver for sprint retrospective

[@zo7588]

- we must learn from our own mistakes - Three pillars of the empirical cycle include: Transparency, inspection, adaptation - PDCA: Plan, Do, Check, Act ; SCRUM is an empirical process

[@MasoumehGholipour-h8t]

A.(I/A)Inspect and adapt to ensure the delivery of valueable product and there is desire for that B:Collaboration and prioritize value creation C:Achieve goal via strategies.

[@stephanttqqqqqqtqqqqqqqqqq5668]

key takeways: - learning from our mistakes/experiences - continuous improvement - process of do/see results/analyse/infer/plan - empirisicon cycle of plan/do/check/act (PDCA) - I/A -

[@williampoletto9518]

Key takeaway: sprint retrospective as an opportunity to asses on how things were done and potentially improve processes and tools

[@mvrsrivatsava13]

Key take aways: Retrospective where we document lessons learnt. Empiricism. Plan do check and act. Evolution of retrospectives.

[@sanjeebkumar8843]

Key takeaway: Sprint retrospective is a meeting at end of sprint where we discuss to continuously improve on various parameters and become effective and efficient. It also explains the role to be played by Scrum master, Team member and manager so that the Retrospective proves to be a way to become more effective and efficient.

[@skhadse]

Key Takeaway: Importance of setting aside specific focused time for analyzing and improving team/individual performance to get better with each sprint.

[@lauraesene4975]

This video has shown the importance of Sprint retrospective which is about continuous improvement.

[@abhishekroy2455]

Key takeaways - 1. understood empirical and PDCA cycle 2. goal of sprint retrospective and including CI in it 3. importance of communicating the challenges

[@gobanarasu]

sprint retrospective goal is to have continuous improvement of the tools and techniques, strategies, people aspects, process aspects, relationship , management, culture... moving to be effective and efficient in our work

[@akbarabbas1567]

Key takeaways: • Importance of sprint retrospective • Importance of continuous improvement • what went well, what went wrong, Ideas of the team members, Culture, management, Relationship, process, people, Strategies, Tools and techniques.

[@ashwiniponnachan4977]

Thought for retrospective: - collaborate for continuous effective & efficient - speak about problems - remains transparency, and focus should be to be kept anonymous

[@seshuvutukuri6450]

Key takeaway: Goal of retrospective is for continuous improvement of tools/techniques, strategies, relationships

[@NaveenNanjundappa]

Matured teams shall grow from sprint retrospective to Kaizen

[@curvirao7059]

Key Takeways - Continuous mindset improvement and how each member of the team can develop it and/or educate other team members about. It helps to inspect and adapt frequently and will increase efficiency and effectiveness

[@sridattavirivinti1480]

Key takeaways - It's important to inspect and adapt at the end of the sprint(even though we have daily scrums) which will help us continuously improve over the period of time

[@tanyasharma660]

Key takeaways: 1. Sprint Retro is a continuous improvement process, that must be adopted by each team member for positive continuous growth 2. Role of a scrum master here is to guide and educate the team in regard to Retrospective and why is it significant for a growth of a process.

[@manchalikulkarni5054]

Key Take away: Retrospective helps the team to work towards continuous improvement which reduces the Risk and reduces the cost towards investing on bigger risk. This will also educate the team in improving towards more better and advanced technology.

[@jakobsch8377]

For continuos improvement, sprint retrospective is used to improve based on what went well, bad or not optimally in the last sprint. Another institution of inspecting and adapting

[@baser40]

Key Takeaways: Retrospective - Helps with I/A on what is blocking the team from delivering effectively and efficiently. As MAnager to encourage people to be transparent.

[@MeredithJ-q5x]

3 Key Take Aways: Retrospective meeting tone should be continuous improvement, Retrospective meetings are at the end of sprint, and purpose is to highlight lessons learned with actions of improvement moving forward.

[@Shrie8]

Key takeaways: 1. History and importance of Sprint Retrospective 2.PDCA-Plan Do Check Act and imp of Inspect/Adapt 3. Empirical process. 4. Importance of Continuous Improvement and role in building the Sprint Retrospective Event

[@1901rajan]

1.We should look for continuous improvement 2.It should not held in closed room, it should be public. 3.Team can look for daily improvement but overlooking issue may arise so it is fine to stop at one point i.e. retrospective and look for improvement.

[@prriyamvadhaaarumugam4120]

Key takeaway: Retrospective is an event which is beneficial to team/individual. It makes a clear understanding on how a team/individual can bring effective and efficiency at work where the primary goal is continuous improvement.

[@aafreenqureshi8153]

Key takeaway Retrospective Scrum is a time for teams to reflect on the opportunities to accomplish continuous improvement. The sprint retrospective is a recurring meeting dedicated to review and discuss what went well and what can be improved in a sprint

[@sheshadrireddy665]

Take away : Retrospective is for continues improvement mainly towards process ,t/t..etc

[@RahulKumar-pn2fn]

The key takeaway in the sprint retrospectives is a PDCA cycle in which we do the continuous Improvement process where we inspect the sprint and what went well and needs to be adapted going forward.

[@nigamabhishek001]

Key takeaway: Real objective of Scrum Retro as continuous improvement. PDCA in practice.

[@affannafees7147]

Key takeaway: Retrospective is integral for continuous improvement while the team inspects and adapts.

[@AnandKulkarni-mw8rf]

Key Takeway: Focus on Continuous improvement for Effective/Efficient actions in retrospective meeting.

[@hnhjhaveri1125]

Learn from your mistakes Object of the retro is to get into the mode of continues improvement -Hipul

[@ShrutiAmritphale]

Takeaway: Why retrospective, how to conduct, what are the key outcomes, when to conduct this, what is expected from the scrum team in retrospective meetings

[@unnatimistry4590]

Unnati Mistry CSM batch 29_30 April 2023 Keytake aways 1. Sprint Retrospective is apart of Scrum events which is normally done at end of Sprint after Sprint review.It is a learning process. 2.Team has to focus on continuous improvement through inspection and adapting various tools and techniques, statergies,people and process aspect. 3.Team should be effective and efficient at work.

[@proudkislaya]

Key Takeaway Sprint Retrospective meeting enables the scrum team to become more effective and efficient in their work by focusing on their strategies, tools & techniques. Since the focus is on continous improvement and the team members hold each other responsible, the team undertaking SR meetings emerges more effective and efficient at their work over a period of time.

[@johnsaccardo4064]

Takeaway: Sprint retrospectives should be focused on how we can improve into a more efficient and effective team.

[@jignalodaya4515]

Key Takeaway Sprint Retrospective cycle of PDCA and in this cycle identify the area of continuous improvement of technology, process, people and strategies.

[@maneeshavallamreddy4982]

Key takeaways: PDCA - Plan Do Check Act Sprint Retrospective - To focus on Continuous Improvement of People & Process To be effective & efficient

[@anupmc77]

Sprint retrospectives, continuous improvement

[@bijunija2345]

Key Takeaway How sprint Retro helps in continuous improvements