3 Key Takeaways: 1- Inspect/Adapt + Effective/Efficient Actions = Higher Success: Emphasizing the importance of regular inspection and adaptation, coupled with effective decision-making, significantly boosts the likelihood of success in Scrum. 2- Value Responding to Change Over Strict Planning: Successful teams prioritize flexibility and responsiveness to change, demonstrating that adaptability is crucial in achieving project goals. 3- Scrum is a Framework; Mastery Takes Time: While learning the basics of Scrum is accessible, mastering its principles and effectively applying them in diverse team environments is a more complex journey.

Sir, how to get the CSM renewal certificate? my company is asking me

3 key takeaways: 1- Make strategies by frequently inspecting and adapting to situations 2- Leverage a combination of effective tools and techniques to make work easier, faster and better 3- Align strategies with: scope, cost, time

3 Key Takeaways: * Inspect & adapt, do it frequently *Take effective and efficient decisions *have a single goal in self org team

Is there any weekday class for CSM for this week?

Good session altogether 😊

Thank you sir, great video on learning the strengths of scrum

3 Key takeaways: 1. Inspect and Adapt the situation frequently with an effective strategy building to achieve the goal 2. Adaptation of suitable tools & techniques 3.Meaningful and visible information radiators to inspect and adapt

Naveen, you have nailed it !!!!! unfortunately, there is a huge gap in the industry about basics or Scrum and Agile and respective methods but many don't question the practices followed that's a sad thing. However, it's really recommended to watch multiple time and understand core concepts..

Great one Naveen really enjoyed and the ending statement was completely true still there are many gaps in the organization's strategies that are not matured as per AGILE.

Very informative and agree many are not aware of the core concepts of basics agile and Scrum, and irony is many trainers have this gap too

Hi Naveen, I really love the way using sketches and papers to explain concepts

Great one Naveen

new subscribe new friend

Hello 👋👋👋👋

Incredible

Key take aways: 1. Inspect and Adapt 2. Do this Frequently 3. Make Efficient and Effective Decision Secret to build a Winning Team is to follow Agile Manifesto ie 4 Values and 12 Principles which in turn builds a winning product 4 Values: Individuals and Interactions over Processes and Tools Working Software over Comprehensive Documentation Customer Collaboration over Contract Negotiation Responding to change over following a plan

Beautiful explanation on burnup and burn down charts. My key take aways: 1) pending info is shown using burn down charts. 2) accumulated info is shown using burn up charts. 3) the slope of the graph does not act as a reference for performance judgement. 4) the chart represents a team strategy

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;

Below are my 3 key takeaways, after watching Naveen's video on scrum events: Sprint Planning: - It is happening at the beginning of the sprint; - Answers 2 questions WHAT & HOW? What is the scrum team goal? How is the plan to achieve the goal; - The answers to the above questions are provided by the entire team: PO(Product Owner) & Developers - Sprint planning can last up to 8 hours for a sprint that lasts 1 month Daily Scrum: - It is happening every working day; - PO is optional in terms of presence, while the rest of the team formed by Scrum Master and Developers is a must to attend; - Lasts maximum 15 minutes; - The Scrum team's purpose is to Inspect and Adapt on the plan; Sprint Review: - It is happening on the last day of the sprint; - The scrum team and stakeholders Inspect and Adapt on the 100% done increment (working software) and take appropriate actions; - It is a meeting that lasts up to 4 hours for a sprint length of 1 month;

Below are my 3 key takeaways, after watching Naveen's video on scrum terms: 1. The artifacts of a scrum team are: a. Product Backlog b. Sprint Backlog c. Increment 2. The values of a scrum team are: a. Commitment b. Respect c. Openness d. Courage e. Focus 3. The scrum events are: a. Sprint b. Daily Scrum c. Sprint Planning d. Sprint Review e. Sprint Retrospective

Below are my 3 key takeaways, after watching with high interest Naveen's video: 1. The key to success while adopting Agility is frequent I/A (Inspect and Adapt) + E/E (efficient and effective) decisions; 2. To declare that you are Agile while using the Scrum framework you should know the 4 values and 12 principles of the Agile Manifesto and the rules within the Scrum Guide. The 4 values and 12 principles of the Agile Manifesto are the secrets of a winning team; 3. In an Agile project, that uses the Scrum framework it is strongly recommended to understand what is fixed and what is flexible in terms of time, cost, quality, and scope. Organizations who will consider all 4 as fixed, will fail in terms of agility.

I particularly like the concepts explained here. Its explained in a very practical manner and was easily understood i could actually relate. It is really good advice that in thinking of what is wrong with your organisation and before offering to try to fix it look at yourself and work on yourself first don't try to advice or convince, master your skills and understand the bigger picture as sometimes when you try to advice or fix persons can take it personally and gets offended. but to managers there was also advice and those i could relate to and found very practical. Managers should support the team, build collaborative teams and understand that you cant copy and paste strategies as what works for one organisation will not necessarily work for another. Managers should attend agile training with their teams, this will mean that the team and the managers are being exposed to the same information.

Great video. As a student of scrum i find it a strengthening of concepts learned. my takeaway is that strategies and techniques in and of themselves cant achieve anything they need a 'brain' as you have put it. So for me even the scrum, the best of strategies and techniques are only as powerful, efficient and effective as the individual handling the strategies and techniques. When you said scrum will not increase efficiency i knew that you meant that on its own it wont but its the individual who has to be the one who gets the most out of scrum, the individual and his brain.

As a current student of scrum I am enlightened by this video. It has made several things very clear to me. First of all i am able to understand and appreciate that product owners and developers must work together and work well. Secondly i found the processes easy to conceptualize and relate to...product backlog refinement, sprint planning, and sprint review. The sprint review is of particular interest as it allows developers to inspect and adapt constantly becoming more and more efficient.

Commenting as a current student of Scrum master certification. This video has cleared up an important misconception for me as it relates to acquiring a job after training. I can see that the advice given here is very practical and pertinent as it encourages me as an individual to timely transition into the position i hope for. I'm encouraged firstly to implement scrum in the teams where i work and hopefully the managers will see the impact it has on my department and allow me to implement it on a larger scale. Additionally the suggestion is to look for a job that matches my current capabilities, and which also uses Scrum and after a few years experience apply for a position using scrum master.

Key Takeaways 1. Scrum Master is a mentor to coach the team to work better on their own 2. Scrum master are to serve Team, Org & PO 3. Being the master of Scrum in all areas of the company especially during transition to Scrum - help train, lead, plan, remove barriers etc.

Key Takeaways: 1. Developers are members with multiple skillsets - Coding, Testing, documenting = cross functional team 2. Devs owns sprint backlog, work as a team, PO owns the product, accountable for product, owns product backlog, single individual, needs to ensure backlog is transparent visible & well understood 3. Dev - Focus on building winning product, PO - what makes a product a winning product & managing

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

Key Takeaways - 1. Read these right to left (e.g. Owner of the Product = Product Owner, Master of Scrum = Scrum Master) 2. Scrum Event (4+1) means that SPRINT has 4 events within it: Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective 3. Scrum frameworks includes each one of these - Team, Events, Artifacts & Values

Key Takeaways: 1. Sprints are a measure of time - not exceeding 1 month 2. A Sprint is compromised of the following events: Sprint Planning, Daily Scrum, Sprint Review & Sprint Retrospective 3. Build a goal in Sprint Planning and throughout all other events you Inspect & Adapt that plan as you go (Review = I/A product vs. Sprint Retrospect (related to the people, T/T, strategy) to be used in the next sprint

The key takeaways: 1) SCRUM alone can't make winning teams it's the inspect and adapt mindset with right tools and strategies which make teams win. 2) SCRUM != Agile, Scrum is a framework with set of rules and guidelines, but Agile is 4 values and 12 principles which make teams win. 3) Scrum master is not part of Agile process, but its a role in SCRUM. 4) In Scrum , the team is supposed to be cross functional, i.e the team should have right set of people with coding , testing, automation, documentation capability, Scrum never says the team requires to be having individual who are multi skilled. Multi skill is an advantage but not a requirement.

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.

The takeaways : 1) Sprint planning is the meeting wherein the team mutually agree on the sprint goal. 2) In Sprint planning the team choose a list of PBI in order to meet the sprint goal. 3) Each product backlog item should be broken into tasks, low level design , with Acceptance criteria and DOD clearly understood.

The key takeaways: Scrum values are: 1) courage : The scrum team should show courage to be on right path, asking right questions in right time. Also the team should be courageous to solve tough problems by doing early POCS. 2) commitment : While executing the sprint lots of hurdles would come but the team should be committed to try 100% to reach the goal. 3) focus : As the team is committed towards its sprint goal, it should be focused towards the right set of items to be worked upon to reach the goal, and park unwanted requirements for future consideration. 4) respect : everyone should be respectful towards each other, thus creating a collaborative environment. 5) openness : The scrum team should be open in their sprint execution, risks, impediments, in order to create a transparent system.

The key takeaways: 1) The scrum master ensures that all the scrum ceremonies are carried out effectively within time box. 2) The Sm helps the team to be a self organising team who can resolve their conflicts, carry out inspect and adapt on sprint PBI and create product increments which are 100% DONE. 3) Helps the PO and dev team understand the need of backlog refinement and creation of small backlog items with clear and concise details for working. 4) Helps PO to define the release strategy in complex zone , wherein all the 4 params of release can't be fixed. 5) Coaches, leads, mentor the organisation during scrum adoption, and the need of scrum as an inspect and adapt framework to solve complex domain problems.

Takeaways: Developer responsibility: 1) creating of sprint backlog, implementing product backlog items which meet 100% DOD, inspecting and adapting on backlog items, to meet sprint goal. Product Owner : 1) End -to- end owner of product , from inception to delivery. 2) His one of the main task is creating backlog which is clear, visible and properly defined before the sprint planning. Product backlog refinement: -A session where the entire scrum team meets up to break the large requirement into smaller doable items ready to be inspected and adapted in sprint.

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.

super explanation

3 takeaways 1. In the complex zone, Inspect and adapt Reduce the risk Make it small 2. Each plan and stategy is different. Dont copy. 3. Its always the team who work towards achieving common goals. Trust your team.

Key Take aways : 1) Sprints are cycles of inspect and adapt , which can be max of 1 month. 2) Sprint comprises of sprint planning, daily scrum, sprint review and sprint retrospect. 3) In each sprint event we perform inspect and adapt , to keep risk small. 4) Sprint planning=> max 8/1month sprint, daily scrum=> max 15mins, sprint review=> Max 4hrs/1month sprint, sprint retro=> max 3hrs/1month sprint.

Key take aways: 1) Scrum has a well defined set of scrum team members, events, artefacts, values. 2) A clear understanding of these items helps to understand Scrum better.

Take aways: 1) Character of a winning team is Inspect and Adapt, do it frequently, take effective decisions. A team not following these key points irrespective of the process they choose would fail. 2) Learning Scrum is easy, but mastering it is tough, as we can know the rules outlined buy Scrum, but having infinite strategies and tools and techniques for winning, makes it tough to master. 3) Don't blindly copy strategies from others until you understand its purpose. 4) Agile 4 values and 12 principles are the secret of winning teams. 5) Teams which always have a winning mindset , choose strategies to help them win, and that's the basis behind self organising team.

Thanks a lot for clarification sir

3 Key Takaways: 1. Working Agreements are activities/behaviours, i.e mutually agreed upon, for which each team member is accountable for in order to meet the goal. 2. It's not limited to scrum team, management & customers can also be involved. 3. It requires values system (Respect, Openness, courage...etc) within the team

Takeaways: - Simply adapting an agile methodology won't fix your problems. - it is not possible to fix all elements, you need need at least one variable that can float when you have uncertainty in your project

Promo-SM

release strategy - plan by product owner to release their product -- how what when

definition of ready, acceptance criteria and definition of done