Category: Agile

One mistake that management force the teams to do… “FREEZE” their sprint backlog Yes, one mistake that management force the team to do is FREEZE their sprint backlog, while the sprint backlog is the development team’s plan to achieve the sprint goal, it is just sufficient and just in time elaborated to focus on one item at the time implementing the functionality and marching towards sprint goal. (Let’s pick more on sprint goal in later articles) Sprint backlog is like your route map, it creates transparency for everyone to understand…

Read More

Strategies for handing the next sprint length after cancelling the current sprint Though Cancelling the sprint isn’t a frequent situation. In Scrum framework it’s at the discretion of the Product Owner(PO) to cancel the sprint if PO realize that the sprint goal and plan isn’t adding value to the product. In Scrum only PO has the authority to cancel sprint. After cancelling the sprint, product backlog is updated with latest priorities and value for the product, any work done during the sprint if valuable is reviewed and rest is thrashed…

Read More

While it’s “easy” to follow scrum in your team, making sure that everyone understood the concept correctly and over a period of time seeing success in team work might be a challenging. Today, I am excited to share my learning for scrum. What is Scrum? Scrum is a development framework of leading agile product. It provide or define a way to achieve winning product and build winning team. Here, two words “Winning Product” and “Winning Team” both are self-explanatory. If you succeed to implement product is nothing but winning product…

Read More

Velocity based planning for better forecast of your team’s work. “How much to pull into the sprint during sprint planning?” In fact for me this is one of the most frequently asked question. This question doesn’t have any answer in Scrum framework, this is more of tool/technique and strategy related question. Let’s explore various strategies to have better predictability. Strategy 1: Pull around the average work DONE SO FAR. In this strategy we find the total 100% work done and total sprints completed so far, this ratio gives us the…

Read More

Secret of delivering projects. We expect Scrum framework to provide answers, describe how to handle our situations and recommendations for solving them. Certainly Scrum fails to answer such question and situations because as a framework Scrum will provide only the structure that is required to inspect and adapt. Expecting Scrum to answer all the questions indicates that we have not understood Scrum as framework. For every framework we will need tools and technique, and strategy to get the best benefits. Scrum is like chess game rules. The player will not…

Read More

SPRINT – Inspect & Adapt. Scrum is an empirical in nature that’s fundamentally uses inspect and adapt loops towards solving complex situations in product development. Sprint is the inspect and adapt cycles, which starts with sprint planning and ends with sprint retrospective. Sprint enables the team to maintain a rhythm and focus on achievable goals every inspect and adapt cycle.   What Successful teams do… Maintain a contact sprint length. Decided as common consensus by the scrum team & business/stakeholders. Plan to reach the goal can be inspected and adapted…

Read More

  While traditional frameworks were more focused on efficiency of individual person for evaluating their performance, that predominantly measure “what” they work on. Agile frameworks focus on self organizing teams, such teams needs to have single and common goal.

Read More

Information Radiators fail because… Not constructed with self-organizing as focus. Not radiating most recent date (live) Not visible for people who use them Teams not sure how to use the data and pattern many more anti-patterns

Read More