Velocity is used for measuring the rate at which scrum development teams consistently deliver business value in other words quantity of work a team can accomplish within a sprint. In simple terms, velocity is the sum of the story points that a team can deliver in an iteration. It can be measured in terms of […]
Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. It is a platform for feedback and a cornerstone in the foundation of iterative excellence. Sprint Review is held at the end of the Sprint before the Sprint Retrospective. It is critical that both the Scrum Team and the stakeholders attending understand
Sprint Review: How to be effective Tips and Tricks Read More »
A Program Increment (PI) starts with a time-boxed PI Planning event in which the Agile Release Train is responsible for planning & delivering incremental value in the form of working, tested software and systems. This is a two-day event where all stakeholders (including Agile/Scrum Teams) on the Agile Release Train (ART) participate in a collocated event.
4Ls stands for Liked Learned Lacked Longed and it is a brainstorming technique for collecting feedback on a recently completed project or piece of work. This retrospective highlights the positive (liked & learned) as well as the negative (lacked & longed for). The team has to think mostly from a factual (what happened) perspective, rather
The Sailboat Retrospective is a fun and creative way for teams to reflect on the sprint and identify areas for improvement. It’s called “Sailboat” because the metaphor of a sailboat helps the team visualize their journey, the obstacles they faced, and the direction they want to sail towards in the future. The Sailboat or Speedboat
The Starfish Method for Sprint Retrospectives is an easy way to achieve focus, give a voice to every member, and foster the thinking around practices and the value the team gets from them. It helps teams reflect on varying degrees of actions and activities rather than simply the traditional what went well or what did
A Mad Sad Glad retrospective is a simple and effective way for teams to reflect on their previous sprint. It involves identifying things that made the team feel happy, things that made them feel sad, and things that made them feel angry or frustrated. By focusing on these three areas, the team can identify what
Start Stop and Continue is a great format to focus on the things that are working (CONTINUE), things that are not working (STOP), and things that the team should start doing (START). Its focuses on the past, present, and future at the same time. It is an action-oriented retrospective technique that encourages participants to come
Product Backlog Refinement consists of Creating & Refining User Stories, Estimating User Stories & Product Backlog Prioritization. It is the act of adding detail, estimates, and orders to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Scrum Team collaborate on the details of the Product Backlog,
Product Backlog Prioritization – Tips and Tricks Read More »
Many teams use the Definition of Done (DoD) to check if a user story is finished and the product is ready to be delivered. But what about the user stories that a team receives from their product owner? Teams can check the quality of the user stories using a Definition of Ready. While the value
DoD (Definition of Done) Vs DoR (Definition of Ready) Read More »
Definition of Ready is a set of agreements that let you know when a user story is really done, the team makes explicit and visible the criteria (generally based on the INVEST matrix) that a user story must meet prior to being accepted into the upcoming iteration. The Definition of Ready is a different concept. It is a set of
Definition of Done is an agreement between Development Team and the Product Owner on what needs to be completed for each user story so that it can be satisfactorily verified and validated – usually in the form of a clear and concise list of acceptance criteria that a software Increment must adhere to for the
3C’s is an Effective User Story technique. 3Cs: Card, Conversation, and Confirmation. The Card is the index card that the User Story is written on. The index card format serves two purposes: To write requirements on index cards, each requirement has to be small and self-contained; this helps us focus on what we need to do for
Effective User Story – Card, conversation, confirmation Read More »
INVEST, DEEP , SMART & Three C’s are Effective User Story Techniques. INVEST is a useful mnemonic established by Bill Wake in Extreme Programming Explored. It can be used to inspect the quality of your user story by validating it against each of the following (in Bill Wake’s words): Effective User Story Techniques – INVEST Independent – Each User
Effective User Story Techniques INVEST DEEP SMART 3Cs Read More »
Daily Scrum Anti Patterns are habits that are frequently exhibited but overall ineffective counterproductive in practice or maybe even harmful. Scrum stakeholder anti-patterns result from a training and coaching void accompanied by not changing individual career objectives. “Scrum is like your mother-in-law. It’s constantly pointing out your shortcomings.” — Ken Schwaber Daily Scrum Anti Patterns
Daily Scrum Anti Patterns – Tools and Techniques Read More »
The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master Role is to helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren’t. So the Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team. Scrum
The Scrum Master is a servant-leader for the scrum team & helps outsiders in understanding scrum. Scrum Master tools helps him/her to effectively perform this role. He is a coach & mentor for the scrum team. Coaching is unlocking a person’s potential to maximize their own performance. Mentoring transfers your agile knowledge and experience to the
Agile Glossary and Terminology: Agile Methodology is an umbrella term for several iterative and incremental software development methodologies. This Agile glossary is meant to represent an overview of Scrum-related terms. Some of the mentioned terms are not mandatory in Scrum, but have been added because they are commonly used in Scrum.To learn more about the
Planning Poker is a consensus-based technique for estimation, mostly used to estimate effort or relative size of development goals in software product development. Planning Poker is done with story points, ideal days, or any other estimating units. The Scrum Master, Product Owner, and the development team participate in Planning Poker activity. Purpose: Estimate the effort
A user story describes how the user will use the software in just a few sentences. User stories can be used to represent a new feature, an enhancement to an existing feature, a technical task (like a nonfunctional requirement), or a defect unearthed during testing. As a < type of user >, I want <
User Story – How to write effective user stories Read More »
Studying and Dissecting a problem to identify the root cause is called Fact Based Analysis. It also evaluates potential solutions to ensure it is being implemented in the most beneficial way. Below mentioned techniques can be applied during Sprint Retrospectives. The problem-solving process in fact based analysis has six steps: Define the problem Analyze the problem
SAFe Agilist is a Scaled Agile Framework® (SAFe®) enterprise leadership professional who is part of a Lean-Agile transformation.The course materials are an essential artifact and can be downloaded from the SAFe Agilist Community Platform or can be referred from the website links provided below . These materials can be used to refer back to the
RAID Analysis is an acronym for Risks, Assumptions, Issues, and Dependencies. All projects large and small have risks, issues, dependencies, and assumptions. Managing them is one of the most time-consuming activities but done well, the effort is paid off by fewer delays and cost over-runs, better-informed stakeholders, more support for the project, and better delivery
RAID Analysis: Risks, Assumptions, Issues, Dependencies Read More »
Daily Scrum (Daily Stand Up or DSU) is a reoccurring event to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. Daily Scrum provides at least one daily opportunity to synchronize work and plan for the day ahead. The Scrum Master ensures that a Daily Scrum
Sprint Planning meeting is conducted before the start of a sprint. The purpose of this meeting is to determine the sprint plan and set a sprint goal. This meeting is split into two sessions. In the first session, the product owner reviews the list of features and defines what needs to be built during the
