We have finite time at hand for everything in this world. As human beings we often don’t place a start and end time for many activities of our life.

Planning is an essential, inevitable and very first phase of any project be it a conventional project or an Agile Project.

User stories are single line requirements in the form of a story of what an end user wants and why. An ideal user story format followed by the industry is..

Struggling to differentiate between an epic and a user story in Agile? Wondering if the requirement you have should be treated as an epic or a story?

Agile recommends teams to be cross functional and that implies teams to be composed of people with different skill sets who can convert a requirement into a working software.

Planning, no matter what the occasion, happens almost everyday.
Planning is an activity which describes the activities , resources, timelines needed to deliver the output in the question.

One of the major challenges we have encountered during agile transformation journeys at our clients is to solve how to ensure that Product Owners write good user stories!

One of the major challenges we have encountered during agile transformation journeys at our clients is to solve how to ensure that Product Owners write good user stories!

A cross-functional team is a group of people with all the required skill sets to work together and finish a specific task without dependencies on people outside the team.

Scrum Master is an important role in the Scrum framework who keeps the agility intact within the team. Scrum master plays two roles within the team one is with …

It won’t be an exaggeration to say that out of the millions of Agile practitioners, the majority is stuck at ‘doing agile’ while being unaware or worse ignoring the bigger picture. Why?

Scrum doesn’t inherently prescribe any set day to start a sprint. This begs the question if the topic bears any merit. And if yes, then what might be the best suitable day to start a sprint?

In an Agile project, one most misunderstood concept, which is vital for the project is “Velocity”. While different teams understand velocity in their own way, this blog aims to explain what is “Velocity”?

Product Backlog is a vital aspect / artifact in an agile project which helps the team and the management to keep track of all the items that need to be finished

A scrum master is a team member mostly working towards keeping the agile principles intact within the team. A person who is responsible for facilitation

Surprisingly, most teams following Scrum see Daily Scrum Meeting (DSM) as just a 15 min ritual – one where teams get together to exchange updates.

Sprinting is all about improving the product, process and people. Retrospection is the last ceremony in the sprint which helps enable the teams to improve their process and people front.

If you are looking at scaling agile in your organisation and are considering the Spotify model as one of your options , you have landed at the right place. In this blog, we will attempt to explain..

If you are a scrum team member practicing sprints for some time then you may have encountered confusion around story points & velocity. Here are the few commonly asked questions..

This blog’s main idea is to guide project teams to make full use of JIRA to run a scrum project. Jira is a sophisticated tool which is highly designed to run Agile projects. With predefined templates, boards, reports and metrics..

This article is an attempt to pen down a few hygiene elements to bear in mind while planning your PIs. Sort of a checklist that is drawn from our coaching experience and exposure to various pertinent best practices.

Like any other assessment, agility health assessment also happens at every state of agile implementation & that too frequently. We have used them in measuring the maturity of agile implementation

A good coach is the one who shares the goals with you & works hard till you achieve them. My journey as a coach began in 2013. Frankly, speaking I wanted to work in agile space and found a job with the title Agile Coach.

Goal setting for the teams around strategic objectives has always been prevalent. Why the new interest in OKR? The answer may lie in the huge traction and adoption of Agile across organizations.

A “Team” is generally defined as a group of people. Who work together towards a shared goal. In my experience, effective interaction forms the bedrock of such a ‘team’ – a factor often taken for granted. All the more true in an agile environment, where one sees high levels of ambiguity, uncertainty and diversity.

How do we better utilize our time attending an insane number of meetings? Coaches get this asked a lot. While little can be done about the number of meetings just like driving in bumper to bumper traffic, we can surely improve the in-car time utilization!

In Scrum framework, retrospective is the last event of each sprint and has also been one of the most rushed events in our experience. This has meant that the event has failed in helping the team, consequently failing in its purpose and has thus been considered mostly as an helpless event.

Scrum Alliance has published seven versions of Scrum Guide in a decade since the first version was published in 2010. Each version has been a reflection of the changing landscape of software development processes.