Scrum Master Archives - Tech Agilist

Impediments: Examples and Strategies for Scrum Masters

Mastering impediments is crucial to the Scrum Master’s role in fostering a high-performing Scrum Team. Impediments are obstacles that hinder the progress of the Scrum Team in achieving its Sprint Goal. They can come in all shapes and sizes. They can be technical (missing resources, software glitches), organizational (unclear priorities, stakeholder interference), or even interpersonal […]

Impediments: Examples and Strategies for Scrum Masters Read More »

Context Switching – Measure and Avoid

Context switching refers to changing focus or shifting attention from one task or activity to another. In the context of software development or project management, context switching often refers to the practice of moving between different tasks, projects, or priorities. There are several implications and challenges: Loss of Productivity, Reduced Concentration, Increased Errors, Delay in

Context Switching – Measure and Avoid Read More »

Motivate People to Use Scrum – Strategies and Examples

Embracing change is never easy, especially when it involves a shift in work methodology. Motivate People to use Scrum. Introducing Scrum to a team that is resistant can be challenging, but with the right approach, it’s possible to motivate even the most reluctant members. Motivating people to adopt Scrum, especially if they’re initially resistant, requires

Motivate People to Use Scrum – Strategies and Examples Read More »

Test Driven Development – Agile Practice

Test Driven Development (TDD) is a software development approach in which developers write tests before they write code for new features. The code is changed to make the tests pass and subsequently, is refactored to meet the functional and non-functional requirements. This sequence of steps is repeated until all test cases for all features pass and can

Test Driven Development – Agile Practice Read More »

KANO Analysis Model – Value Based Prioritization Techniques

Kano Analysis Model is a Lean Six Sigma tool that helps us prioritization of product features, and we can understand the trend of satisfaction level of our customers. Most of the prioritization techniques are based on business values & over a period of time, almost all features expected by the user will get categorized as

KANO Analysis Model – Value Based Prioritization Techniques Read More »

MoSCoW – Value Based Prioritization Techniques

MoSCow prioritization technique plays a key role in Agile Project Management. In traditional projects, teams balance the ‘triple constraints’ of Scope, Time, and Cost. For Agile projects, however, the emphasis is on continuous value realization for the end customer. The triangle structure can be reused, but with a set of different vertices, namely – Value,

MoSCoW – Value Based Prioritization Techniques Read More »

Successful Scrum Master – Tips & Tricks

A successful Scrum Master ‘s key responsibilities include creating successful scrum teams with strong skills in self-organization and cross-functionality and a drive for continuous improvement. Helping & supporting Product Owners in visualizing progress, creating a transparent Product Backlog, and maximizing the value of the product. Helping organizations in making & successfully adopting Scrum by supporting management in changing processes,

Successful Scrum Master – Tips & Tricks Read More »

Sprint Retrospective – Tips to improve & spice up

Sprint Retrospective is to plan ways to increase quality and effectiveness. It is an opportunity for teams to reflect on their journey, refine their processes, and set the stage for continuous improvement. This blog unravels the significance of the Sprint Retrospective, exploring its purpose, key practices, and the transformative impact it can have on team

Sprint Retrospective – Tips to improve & spice up Read More »

Technical Debt – Tips and Tricks to Avoid/Manage

Technical Debt is the collection of design or implementation constructs that are expedient in the short term but set up a technical context that can make future changes more costly or impossible. In other words, Technical Debt is the deferment of good software design for the sake of expediency. It presents an actual or contingent

Technical Debt – Tips and Tricks to Avoid/Manage Read More »

Affinity Estimation – Agile Estimation Method

Affinity Estimation is a technique many agile teams use too quickly and easily estimate a large number of user stories in story points. Other estimation methods like Planning Poker or Bucket System are effective methods of establishing consensus in small projects. Affinity Estimation is a great technique if a project has just started, and have

Affinity Estimation – Agile Estimation Method Read More »

Dot Voting – Agile Estimation Method

Dot voting is usually considered a decision-making tool, not an agile estimation technique. For example Dot Voting is preferred to select the most important 2-3 items during sprint retrospective. It’s a simple and effective way to prioritize or indicate the value of several small items quickly. When there is a relatively small set of items and

Dot Voting – Agile Estimation Method Read More »

Bucket System – Agile Estimation Method

Bucket System Estimation technique is used when there is a very large numbers of items to be estimated with a medium to big sized group of people, and to do it quickly. This approach provides a consistent way for teams to size stories by discussing each story in terms of pre-defined buckets of complexity before

Bucket System – Agile Estimation Method Read More »

White Elephant Sizing – Agile Estimation Method

Agile teams need to estimate the size of their stories or product backlog items. The goal of the White Elephant Game is to get a quick estimate of the relative size of an agile project and the size of the individual stories before the project starts. It gives opportunity to everyone for their voices to be

White Elephant Sizing – Agile Estimation Method Read More »

Agile Scope Creep with Examples

Agile Scope Creep describes how a project’s requirements tend to grow over time, goals, or vision changes beyond what was originally agreed upon. Scope creep is frequently caused by changes in project requirements from key stakeholders (not properly defined requirements and additional features are added to an existing product), as well as internal miscommunication and conflicts.

Agile Scope Creep with Examples Read More »

Power Interest Grid – Prioritize Stakeholders

A Power Interest Grid is a matrix used for categorizing or prioritizing stakeholders during a project to allow them to be effectively managed. Stakeholders are plotted on the grid in relation to the Power (Y-axis) & Interest (X-axis) they have in respect of the project. Charting the relationship between different stakeholders is the best way to

Power Interest Grid – Prioritize Stakeholders Read More »

Ishikawa Diagram use in Root Cause Analysis

Ishikawa diagram is a graphic technique, that is used for displaying the characteristics of a given situation or problem. It is also known as Fishbone Diagrams, Herringbone Diagrams, Cause-and-Effect Diagrams, or Fishikawa. Ishikawa diagrams are used for defect analysis (Root Cause Analysis). It is very useful when the analyzed defect has multiple causes. A problem

Ishikawa Diagram use in Root Cause Analysis Read More »

Tuckman Ladder Model – Team Development

Tuckman Ladder Model is one of the models used to describe the process or different stages of team development. These four stages are “Forming, Storming, Norming, Performing, and Adjourning”. Important Points – Tuckman Ladder Model Usually, the stages occur in order. But teams can get stuck in a particular stage or regress to an earlier stage. Projects

Tuckman Ladder Model – Team Development Read More »

Agile Maturity Index & Agile Maturity Level

Agile Maturity Index is a way to know what the degree of maturity of the team is measured by applying some method, practice, or work technique, to know the level of mastery and the degree of adoption of Agile. It gives opportunities for improvement by challenging the team to implement the best-recommended behaviors to be

Agile Maturity Index & Agile Maturity Level Read More »

Planning Onion – Levels of Agile Planning

In Agile planning, there are many layers of planning involved, which gives the name “ Planning Onion ” to Agile planning. Agile does a lot more planning because it focuses more on frequent planning sessions instead of comprehensive planning that mitigates the risks of longer terms. The Planning Onion helps teams choose the right level of planning

Planning Onion – Levels of Agile Planning Read More »

Stakeholder Engagement & Management in Agile

Stakeholder Engagement and Stakeholder Management are arguably the most important ingredients for successful project delivery. Stakeholders of a project are individuals, groups, or organizations that are affected or perceived to be affected either positively or negatively by a decision, activity, or outcome of a project. A stakeholder group can help it live out the pillars

Stakeholder Engagement & Management in Agile Read More »

WSJF – Weighted Shortest Job First Prioritization Technique

WSJF is a Prioritization method that helps calculate and understand what is the level of the financial impact of not finishing the task or implementing the solution sooner than later. a prioritization model used to sequence jobs (eg., Features, Capabilities, and Epics) to produce maximum economic benefit. At the end of the calculation of the

WSJF – Weighted Shortest Job First Prioritization Technique Read More »

Agile Estimation Techniques

Agile Estimation is the process of finding an approximation level of effort, which is a value that is usable for few purpose even if input data may be incomplete, uncertain, or unstable. Traditional waterfall method uses bottom up approach with the smallest tasks at the bottom. But agile uses two estimation techniques,Top-Down Estimation and Relative

Agile Estimation Techniques Read More »

Burnup Chart – Sprint & Release Tracking

Burnup chart is used to show how many story points are in the product backlog versus how many we’ve completed till date, as well as how much work remaining in the project (Not on Sprint level but at project level). In other words it displays the scope of a project and the work completed. Burnup

Burnup Chart – Sprint & Release Tracking Read More »

BurnDown Chart – Sprint, Release and Product Tracking

A Burndown chart is a graphical representation of work left to do versus time. Each point on the chart shows how much work was left to do at the end of that day (or week, month or other time period). In the Daily Scrum the Development Team updates the Sprint Burndown and plots the remaining work of the day. It is a chart

BurnDown Chart – Sprint, Release and Product Tracking Read More »

Velocity vs Capacity in Sprint Planning

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

Velocity vs Capacity in Sprint Planning Read More »