Theory vs. practicing the theory

Part 3: Practicing Agile – “the other anchors in the sailboat called Agile”

 
As discussed in part 2 of the “theory vs. practicing the theory”, are people (management/business) the only possible challenges to successfully practicing agile? Well, they may be the ones, but they are definitely NOT “the only ones”.
Trying to execute an Agile methodology without understanding it well, in itself creates problems in the long run. Organizations often choose to execute projects/programs using Agile without even being very clear about  (and this may not be an exhaustive list) –
  1. What problem are we trying to solve?
  2. Will Agile solve all the problems? Or will there be others that’ll need to be approached and addressed differently?
  3. Are the ways of working and the expected outcomes clearly understood by all the stakeholders and the team(s) on the ground?
  4. What is the common understanding of VALUE and is the focus more on delivering value rather than meeting schedules?
  5. Do we have a clear and well understood definition of MVP (minimum viable product) and is it something that gets refined with the stakeholders periodically, based on changing business/factors driving the market?
  6. Do we have the right tools (CI/CD) and/or practices (XP, DevOps etc.) in place to support continuous delivery of value (by making inspect and adapt processes transparent, effective and frequent)?
  7. While the teams may bend and twist the processes, and use the agile lifecycle management tools in the way they like, does everyone share the same mindset - the one that’s recommended in the agile manifesto?
  8. “A tool is only as good as the user is”, and if teams think that using the best tools in the market will fix all the issues then they’re digging their own grave!
  9. Are teams able to identify “waste” and eliminate it thereby leading to continuous improvement?
  10. How lean are organization processes? Do these processes allow teams to focus more on creating and delivering value rather than managing reporting requirements, creating/maintaining artifacts and appraising stakeholders of the progress?
More to come and if you all have more items to add to this list, please do. Signing off for today!
 
Happy reading,
Jasdev Singh (PMI-ACP, CSM)
https://in.linkedin.com/in/singhjasdev
 

Comments

Post a Comment

Popular posts from this blog

Increasing your Agile Team's Outcome Predictability

Image
Understanding Predictability in Agile Team Outcomes   "Understanding Predictability in Agile Team Outcomes" refers to the study or analysis of how consistent and reliable the results or achievements of a team practicing agile methodologies can be. This involves examining the factors that contribute to the team's ability to deliver on time and within scope, as well as identifying potential challenges or obstacles that may impact their predictability. By understanding these dynamics, organizations can better manage and optimize their agile teams for more consistent and successful outcomes. In today's rapidly changing world, the significance of accurate weather forecasts cannot be overstated. Similarly, in the world of software development, predictability is crucial for Agile teams. The ability to deliver outcomes predictably is a key factor in Agile team success. Achieving predictability can be challenging for Agile teams due to various factors such as capacity planning
Read more

Stop starting, start finishing.

Image
Limiting WIP & reasons for high WIP My first post on Kanban  deserved a sequel for sure! While it isn’t possible to have literally no work in progress, the overall goal of a project team is to finish as many things as they can, and not be in a state of continually starting. Having too much #WIP makes this goal even more difficult.  The impact of too much WIP on efficiency and throughput is one of the reasons it is often regarded as a concern. According to studies, the cost of context change is frequently far more than people anticipate. It is evident that dropping one object and taking up another cannot be done in such a way that no time or energy is spent between the two. However, there is sufficient evidence to suggest that the loss is rarely worth the gain. These apparent consequences of having too much going on are easy to identify once you know what you're looking at. Looking around the team, you'll notice that there are many tasks open, few of which are done, and many
Read more

Mastering the Daily Scrum

Image
- A Key Ingredient for Agile Success Introduction: In the fast-paced world of software development and project management, staying on top of tasks, priorities, and progress is essential. The Daily Scrum, often referred to as the Daily Standup, is a cornerstone of the Agile methodology. It's a brief, focused meeting that empowers teams to synchronize, collaborate, and make data-driven decisions. In this blog post, we'll dive into the what, why, and how of the Daily Scrum to help you harness its potential for your agile projects. What is the Daily Scrum/Daily Stand-up? The Daily Scrum is a daily ritual (a scrum event) that brings the entire team together for a brief, time-boxed catch up. Its primary objectives are: Synchronization: Ensure that everyone is on the same page regarding the sprint goal and knows what to work upon given the priority. Collaboration: Encourage open communication among team members. Identify and Remove Obstacles: Highlight any impediments that need res
Read more