Is it simple to practice theory?


Theory vs. practicing the theory

Part 2: challenges in practicing agile theory


So … we looked at the agile manifesto and the “people side” of things that it talks about in part 1 of “theory vs. practicing the theory”.

The second part focusses on - What makes agile theory difficult to put into practice? We’ll get a better understanding if we start by looking at who’s involved in software development using agile methodology (and I’ll stick to scrum here to keep it simple).

Here are the key players –
  1.  The three roles in scrum: product owner (PO), scrum master (SM) and the development team
  2. Various management roles (you can’t do away with management, can you?) – project manager, program manager, delivery manager, engagement manager or whatever name you like to give to that “authority”
  3. Business stakeholder(s) or those representing the market
  4. Project/program sponsor(s) putting their money into the venture


Looking at the list of key players above, it doesn’t take rocket science to figure out that the third and the fourth roles above, are the ones who are more concerned about meeting the schedules than understanding/accepting the challenges of the team on the ground.

That said, you’ll often hear the “management” saying - it doesn’t matter whether the teams use agile or waterfall to manage the software delivery life-cycle; at the end of the day, what matters is that the delivery should be flawless w.r.t. quality (zero defects), with minimal (in fact zero) cost and schedule overruns; no mention of scope changes!

In this tug of war between the team, management and business stakeholders, it becomes challenging for teams to stick to the agile mindset/values and principles. While the team’s scrum master may give his best to ensure agile scrum practices are followed, the management may be least bothered about it.

At the end of the day, focus changes to “doing Agile rather than being Agile”!

Best,
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