Tag Archives: Sprint

Waterfall inside a Sprint

There were 2 serious problems that we encountered and learned from our mistakes. We were biased with waterfall model or the only model that we knew how to manage / run a software project.

Running a waterfall model inside a sprint.


When the sprint starts rolling even on the first day, a user story is taken by a developer and starts to actual code the piece of information. At the same time the tester creates the test scripts based on the test plan detailed in sprint planning.

On the day one, the daily standup are normally missed or happens for less than 10 minutes for the working group to pickup on the activities that they have agreed on the Sprint Planning. For a 30 day Sprint, effectively we would have 29 Daily Stand-up’s. On my observation, I have found 20% of 29 days to be greatly effective and remaining 70% is just tracking and in progress status and 10% of 29 days to be very ineffective.

The 20% is again split up in the start of the sprint where the coder actually starts working on the first piece where he has actually made his mind to stick with the promised schedule and he gets it 90% of the time. The second gear up actually happen just 2 or 3 days before the sprint ends. The fast tracking or eventually working hard to deliver is in every once mind. Over a period of time, when the team gets matured, they understand this really happens in self organized teams.

The 70% is the actual threat where we by mistake fall into a waterfall model, unknowingly due to delays (may be) even from a single resource standpoint. Once a delay is found or the velocity of the team moves to and fro, the shift affects the next step to happen. (That itself falls unknowingly, into waterfall)

The developer delayed the process by 2 days and starts to work on Task B with a delay of 2 days, the tester has no work for 2 days, including the other parties, over a period of time, we could see the developers creates function after function and tester testing features after features inside the sprint, we run a waterfall without even knowing its run one after the other, one being depended on the other, one waiting for work and one extending or delaying what was promised.

It is actually a complicated process to run parallel, with test sprint run to find the team’s velocity and over a period of executed content, it gives you the truth, the fact of what really can be delivered as a team, not as an individual. The PDCA cycle pulls the dirt and show off the real threat.

A highly self organized team provides 100% results. The threat is not if they produce less than 100%, the threat is when the team produces more than 100%. The Scrum Master changes the velocity of the team and it grows with a decent run. Most of the times, in my practices, I have seen teams take the best velocity to run the sprint, on the 70% in progress meet-ups on daily scrum, they take more user stories performing the actual calculation of Sizing, Duration fix and Schedule draw. And on the flow, the user stories that have picked up are left without a single work done due to the test bugs that had to be reworked or completed in full that pulls the velocity of the person or the team to a positive side. On the next Sprint if the Scrum Master decides to go with the best bet for the resource, It becomes even more a cumbersome process to detail the real value. Its fine if the velocity and the deliverable can be managed but each time the sprint runs, it has to be managed well. The Scrum Master gets the experience of validating the real velocity to go in comes with running few sprints and experience.

The problem of estimating features is a continuous process as features are always and mostly different from one another. When we spend time to create a feature and label it “Done” we also take a measure to see if that can be automated. The time taken to automate the feature would be normally 5% of the estimated user story size. This is sometimes a kill when we automate a feature and when we try to use it, the same 5% goes in integration even if the feature is ready to plug and play. The save is only for the testers who do not recreate the scripts to run.

We have our User stories complete, An acceptance criteria and a proper done statement, Next in line are estimating the size, Deriving a duration (using the velocity) and draw a schedule. We do them one after the other and continue till we reach the end of the velocity. Here we are running a clear waterfall model that can’t be stopped. Over a period of time, the team understands with a shock on both the cases to feel that they are not doing an iterative mode. They have unknowingly trapped in the waterfall model and the way to stop is to terminate the sprint and start working on with the Sprint Review and Retrospect to identify where we could change.

Terminating a Sprint is not as easy as it takes, as we would be running in the 70% in progress status. There are deliverables half done and team members waiting for their share to shed. It becomes a cumbersome war in between the team to deliver. The elasticity of the team would help it bring over few portions of digestible delivery. If the Sprint is terminated and has to restart, the work doesn’t restart from scratch but from the part that was half done but the estimate(size) in full. 


If you are starting to follow Scrum, I would highly suggest to run demo sprint of full 2 rounds with the executing team to understand how it work. Even before following Scrum make sure you have a proper need to use Scrum. Threats like this are lessons learned from my practices.


Posted by on October 5, 2011 in New forms in Agile


Tags: , , , , , , ,


SM Cap


Software Projects fail, mostly in the waterfall model. Period, The Project Manager is blamed at most times. One of the key effectiveness in the failure is the tool-centric process or Process-centric tools. The time taken to effectively learn a process, its entire life cycle and how it could be used is missed drastically by most project managers, even if they are qualified and certified. Agile practices are to be tried to roll to perfection.

Replacing a Project Manager in the middle of the project with another Project Manager is a kill to the project. These risks are never taken and if taken by chance, a clear knowledge transfer (KT) that runs to months are formed by organizations. The question points to why this is a kill? Is the project manager the driver of the project? No. He is the driver of the process. This is missed from the organization point of view. The project changes or fails due to the unclear understanding or misunderstanding by the stakeholders (en all).

These points to majority of the work that is done below: 

  1. Awarding Client relationship and the movement to a new manager is a threat.
  2. Project documents collected and reviewed need to be agreed and reorganized.
  3. Direct Reports have a psychological issue.
  4. The threat of the new manager taking command and new directions along with the results of the direction are threats.
  5. Time to settle down in the new arena is a dead time.
  6. Above all, the organizations power to substitute a time centric manager for an on-going project is critical and a threat.

What if the project is in an agile model with a Scrum Master (SM) at work? These above threats are never felt in the first place. The power of the designation is as simple as a practicing Scrum Master. (above all).

 Scrum Table

I have the art practiced in moving SM from one project to another in different phases of Scrum. I have seen the effectiveness of how a master can work with his inputs to yield super deliverables, “the threat of moving, replacing the efficient Scrum Master is not a threat but the ability the position gives you to handle your projects”.

The Scrum Master is not a project Manager but a facilitator, Coach, mentor and a practice guide. In transforming organizations and transformations projects, The SM is the 361 degree key. (361 degree is a level above 360 as 360 is also 0 at a point in time).

Why do people transform or change the way they deliver software projects?

I have seen projects that span years with their vision statement changing once in year,

  • Changes to the organization hierarchy happen in a pizza move.
  • Alignment to the Business Idea or Value,
  • Core Strategic makeover,
  • Technology subversion
  • Logistical transformation
  • Cultural dependencies
  • Compliance guarantee. &
  • Requirement for a project all keep changing all the time, just to reflect what the business ultimately wants to do.

Improvise trends, use newer, safer technologies and work with unanticipated change and anticipated risk has become more of a sign language. Leaders in the organization think wide with the current role or fade it away with their juniors who are informed leaders at most times and just plug and play the game called change.

Today Leaders showcase “Change” as a centric, dynamic and objective oriented approach with a strategy build over in multiple loops. Yet they fail to deliver what is expected at the end of the deliverable. As I have seen it, the failure itself brings the need for the change. Then there is another new game to start with.

End of the deliverable is what needs to be changed. The deliverable should be progressive, measured and on the move of inspect and adapt approach. In-fact other than the software development industry (as a whole), most business does a unknown mistake and learns from it, recovers from it and draw a tar road to allow people to follow and miss the holes. But here, in the software development industry, there are proven ways to fall and ultimately points to the managers who hold the failure. The failure is known for sure over the period of changing. The only reason is because the organization focus is on the change and not on the fall back of the change. The sure reason why Scrum is effective today is for the same reason.

Today, the software industry needs the change to prove the platform can be solid to multiply its branches above than re-engineering the platform, again and again. The computing industry is starving with known failures from the waterfall model and each organization has in one way or the other seen, felt and failed multiple times.

Change itself should be digested as a process than looking at it as a new paradigm in shift. The core of change is static, if a change is envisioned to a business model of shifting things or a strategic change to pull over sheets of vertical and horizontal moves, it still doesn’t change the core of applying process to a set of defined way of working. This can be termed as Change Innovation. Where change is continuous and the methods or approach towards them are new. 

The guy who is ready for the change, ready to take the ball and being prepared to play the Rubix from any point is a Scrum Master. He understand where he stands now, what he needs to do, perform a change when required and go back to the place he belongs.

From (Do Better Scrum – Peter Hundermark)

The responsibilities of the SM role are:

  • Empowering and shepherding the team.
  • Removing impediments
  • Keeping the process moving
  • Socialising Scrum to the greater organization.
Recruiting SM

 Recruiting the Scrum Master

Its one of the hard challenges to find a really qualified Project Manager to manage a similar, scaled project. Its quiet easy to find a Scrum Master.

 While recruiting a Scrum Mater, I have found and used the following:

  1. Is the master trained?
  2. Is the master certified or planned for a certification?
  3. Can he present what lessons he learned while practicing scrum?
  4. Can he start a new scrum team and follow process?
  5. Is he detailed oriented?
  6. Does he have the courage to speak what the truth is?
  7. Ways that he performs a Sprint Daily Standup?
  8. Ways he helps / coaches to clear away impediments
  9. Solutions that he can bring in a scenario.
  10. His skills in introspecting and retrospecting.
  11. Can he follow process? ( I don’t want a innovator here)
  12. Finally, what is his personal interest in growing up?


Forming a new Organization Change (Role of the SM)

The framework which is the body of Scrum should be well defined by a SM. He should be able to adapt himself best as a coach, to a mentor and facilitator when needed.

As a coach, I would admire the capabilities of a SM to teach the basic principles. Stick with time-boxed practices, detail results of what was expected and if it was achieved and further to anticipate and work with risks that he may come across in the future.

Even though risk planning is not a part of the game and we require it on daily basis to understand while working with impediments.

As a mentor, I would like him to scale from a manager to boss, to make sure peers follow procedure, understand and create a cross functional team, work with multi talents and have a clear collaboration ticket while dealing with resources.

There are known risks that I have seen over the past that the mentoring changes to bossing and practise rude rules to follow procedures. I would like to handle them with maturity and politely as possible and when required to be real rude, bring in an essence of the act wouldn’t be willing.

While in the process of creating a self organized culture, we make several mistakes, one of the common one is to forget what the individual tries to achieve as best as it can be. “To code, To test, To deliver”. Scrum is just a walnut shield. The core being nuts cannot be avoided. We need to be matured enough to thing deliver is important in the framework of scrum in regular intervals and we need to keep the space in between to make sure the resource understand the need to deliver in the framework. Mostly of what I’ve seen is the framework being important than the deliverable.

As a facilitator, I would like my SM to be thinking before time, being an active participant in the Sprint Planning I & II, Sprint Review and Retrospect and identify, inspect and adapt principles at all times. He should be a core replacement or sometimes fully responsible for the changes in the Sprint backlog, release planning and burn downs and up charts.

Lastly, I would love him on the attitude he has with the framework, not as an innovator but to ideate process in bringing peers to communicate, collaborate and co-ordinate clearly.

A New Scrum Team

A perfect place, to perform. New organizations or communities of projects that are formed are the perfect place to start a scrum or transform to scrum. Even if the requirements are frozen, estimated and risks analyzed, Scrum gives you the opportunity to gel well.

The Appointed SM, should be a team player to understand what he needs to deliver. Be aligned with the process and make sure he is available at all time with the team to remove impediments.

  • His active role would be to train team members on ground rules of scrum.
  • Aid with Stories, Epic’s & Theme creations.
  • Planning mechanism to size and create backlogs.
  • Spread the value of volunteering, the freedom Scrum gives to perfect what a resource could do all by himself to learn and grow.
  • Practice Daily standups and stick to the time.
  • Make sure the team members efficiently create a self sustained organization of solid deliverable’s.
  • Help team members in show casing what has been completed in Sprint Review and be a proactive member, inspecting and adopting in Retrospect.

Hand in Hand with the Product Owner

Scrum Master and Product Owner should know each other well and have a good rapport.  It is extremely essential to think our product owner is our internal customer. He creates and maintains the Product Backlog with the help of the team. The SM should keep the Product Owner informed at all times, including the Sprint Planning 1 (and if needed) Sprint Planning 2. The major stakeholder’s vision should be digested and the deliverable showcased properly in Sprint Review and Retrospect.

In our office, we have a dashboard in a meeting room where the artifacts are placed at all times. (Prior to use of the customized software program). All our meetings happen in the same room and outside the room we all share common desks other than the Product Owner. PO doesn’t share desks and he is seated at the same floor in corners of the building.

As we work in an Agile Platform, our bills are totally different from waterfall model billings. Each day the Scrum Master takes an extra effort to work down the ‘Resource Allocation Planned vs. Executed’ with the help of burn down charts and actual hours indicated by the resource. We have principled that our offices in India close by 5:30 for all development and testing teams and 15 minutes of time is taken out to fill the hour sheet for that date.

This information is collated and global billing sheets are updated each day, till the Sprint review to create the invoice for the Sprint by the practicing SM. Our clients are well aware of day to day chargeback details as they are available on the Sharepoint that our clients can access.


Sprint, Release Planning 1 & 2

One of the most important activity in Scrum that helps the entire team to focus on risks, estimation, tasks breakdown and incremental deliverables.

SM should invite the Product Owner and make sure his participation is valued as he guides the team in the right direction. SM should also bring in required stakeholders needed to guide the team in understanding requirements.

With my experience, I strongly recommend to have this meeting well planned for a whole day to focus on the requirement and baseline it.

Velocity is planned in the phase, updated on the Sprint Review for the next Sprint.


Daily Scrum Meeting:

The primary host of the meeting is the Scrum Master. A single meeting would be able to show us how the scrum framework is followed in the project. The SM, learns, inspects, adapts and guides the entire team on the next move to win the game.

Few activities in the daily scrum apart from the 3 questions:

  1. Make sure each resource has specific task’s to do.
  2. The task’s are estimated, sized and prioritized (not ordered).
  3. The tasks are in the order of execution or helps to delivery the package to the current Sprint.
  4. Make a note of repeated events and by repeated team members on impediments.
  5. Track and resolve the impediments list on priority (urgency).
  6. Track team members idle time and leave details.

Once the meeting is over, The SM should start capturing values in the Risk Register, Impediments list, Cross check the product Burn down chart and finally inform the Product Owner if there are specific events that needs to be discussed. (Discussions doesn’t happen on daily basis after the Daily Stand-Up, Its only when events or incidents have happened).


Sprint Review

The most crucial part of a Scrum is the Review. In our organization, we have dedicated Quality & Planning team (Q&P) who are a part of each Sprint Review. (They are previously involved in Sprint Planning too). We have divided our Sprint Review into 2 parts.

SR Part 1

Here each resource provides statistics on the individual velocity, no of user stories completed and done. This is compared with the Resource allocation, Task allocation, Product Breakdown chart, Testing related details and Quality Metrics used.

We have brought in Functional Point (FP) Estimation along with PP to estimate sizes for our user stories. The stats are again validated on the SR1.

No demo is showcased here.

SR Part 2

Each resource showcases a demo in an ordered method of their inputs and output and what process has been worked. This confirms with the agreed Done statement of the deliverable which is signed by the SM.

No stats are discussed here.

Our SR’s gives us a clear indication of our agreed ‘Done’ statement to deliver the results for the Sprint. It specifically showcases the “dirt”, both in stats and demos and helps the SM to identify and zero the problem if he has missed it in Daily Stand-Ups and creates a way to rework and adapt an appropriate solution for the sprint.

When the Program / Account / Portfolio manager is involved in a Sprit Review, it helps them to understand how the framework is effectively used or ineffectively individual’s activity and showcases what needs to be done focusing on the solution.


Sprint Retrospect

Immediately follows our Sprint Review on the same day or the following day and no activities are done in between these two meetings.

Notes from the SR Part 1 are taken to make any process improvements, quality changes and allows the SM to guide the team.

The meeting is normally closed door. Only the Scrum members including the PO & SM are involved. Here everyone takes a turn to speak what they have done best and what they could have done best. We also take turn to “Start”, “Continue” & “Stop” activities inside the team.

When SM and PO takes turn to introspect, they make sure they spill the dirt outside and make sure the whole Scrum team works for the vision that has been defined. Many times, in my organization this has become a war room, with maturity over a period of time, we understood what needs to be done as a team than to find difference between each other.

The phase plays an important role if there is a Sprint termination during the execution of the sprint.


SM Artifacts

The SM works with the following artifacts in creating, updating on a regular basis.

  1. Resource Allocation.
  2. Resource Utilization.
  3. Resource Leave Calendar
  4. Notes (from Sprint Planning, Daily Stand-up, Sprint Review & Retrospect and Process Improvement)
  5. Sprint, Release, Impediment & Product Backlogs.
  6. Burn down/up Charts
  7. Risk Register
  8. Velocity Chart
  9. Tools:
    1. Planning Poker
    2. Functional Point Estimation Template
    3. Story Cards
    4. Process Improvement Template
    5. Lessons Learnt Template

Texts marked in Italics are not a part of Scrum and followed by our organization.


Day2Day activities

Tomorrow is just going to be like today as it was just like yesterday is not the agenda for a Scrum Master. Each day is a challenge, struggle, lot of quality paper work and lot of planning to be “Done” to deliver what is planned.

The day starts with a Daily Standup, if necessary Scrum of Scrum, Updates to the burn downs, updates to the resource allocation, utilization, update to the backlogs and reports to the PO.


Sprint Termination

Rarely in a case does the Sprint terminate? I have seen close to 6 Scrum sprints being terminated. One of the obvious reasons where I had found 2 cases where the Master was just a project manager to handle things and the team weren’t educated on what needs to be done from their end. The sprint dint last for 3rd cycle and the backlog was still untouched.

In a particular case, the project manager was a SM had no backlog and had all in his mind the Sprint backlog was a set of requirement documents that kept revisions in the version as detailed design documents.

A recent show that I witnessed was in a transformation project, when they wanted to move from a waterfall model to scrum and moved in the coding phase and started up by having a standup for 2 hours each day. The deliverable was really messy as peers dint want to volunteer to work and the named SM had to push the WBS tasks to each.

Whatz Next to Scrum Master

Moving up the ladder is not so easy, Practicing Scrum as a Master is a continuous learning process as each project differs in resources, magnitude and deliverables. The role helps you to look to a project level, growing up or Scrum of Scrum and becoming a professional or a coach should be the target. Most SM practise coaching as a day to day operation and facilitates process to deliver high valued, incremental deliverables. Using this as your key stone, the next move is to certify yourself in CSP and raise the community and the framework as a Coach.

To conclude, I would use (Do Better Scrum – Peter) words that follows as…

 he SM role must provide process leadership to the rest of the Scrum Team and to the rest of the organization. Classroom training, such as the Certified SM course, is an insufficient means to gain the required tacit knowledge to master Agile practices and the Scrum framework. The team and the organization need the skills of an experienced practitioner to guide them through the maze of challenges they will inevitably face in transitioning to Agile.

Leave a comment

Posted by on September 22, 2011 in New forms in Agile


Tags: , , , , , , , , , , , , , , , , , , , , ,

Agile & Ag_lebra (Algebra)


From my childhood, Mathematics has always inspired me, not as a subject score, but the way basic things  are build & broken, equations expanded & collapsed. It was an exercise to mind to freeze and melt. It was interesting to learn space, graphs and plots and solve equations one at a time to get a definite result and in the case of Algebra, we are sure the result is finite and known at the beginning.

Its is amazing to see the clear overlap using Agile Problem Management techniques, scrum methods to solve a problem, to initiate a process, ultimately to yield a known result. Intersect is so fascinating that we learned and practiced them as we were raised. In current Industry practices what we want to yield is ultimately known or desired or even understood to be known, to Reach to the perfection is where we lack.

Scrum, gives us an opportunity, a clear simple vision to understand how to resolve where we lack, the pathway towards a know destination.  Allow me to give you a solved linear equation:

Solve for x in the following equation:

Complete multiplication:

Group like terms on each side of the equal sign:

Subtract 18 x from both sides of the equation:

Subtract 57 from both sides of the equation:

Divide both sides of the equation by 12 and simplify:

The answer is 

Check the solution by substituting  in the original equation for x. If the left side of the equation equals the right side of the equation after the substitution, you have found the correct answer.

  • Left Side:

  • Right Sides:

Since the left side of the original equation equals the right side of the original equation when the value is substituted for x, the solution  is verified.

You can also check the answer with your calculator: 

  • Left Side:

  • Right Sides:

You can also check the answer by graphing:

(left side of original equation minus right side of original equation). The x-intercept is -5.25.


  • Here Storyboards and epics are defined with a concrete solution.
  • While working in Scrum teams, we choose what to be done and with perform them with integrity.
  • The problem is the current line at work, The solved result is just the line below that makes us break each task to a manageable more concrete finding to another one.
  • Retrospect’s or traceability is narrowed, sharpened and clear to track back the incremental solutions done.
  • Changes are basically a pencil erased solution.
  • Each Standup expands the vision to see where we are, what follows.
  • Each Sprint provides a definite result and a finite incremental release.
  • The graphic representation of the solution is always a breakdown. Just like each statement adds immense value in an linear equation, the points in a product breakdown or release breakdown provides us a vision and slaps us of what we have done and reminds the target fluctuations.
  • The parts of the incremental release is a fantastic finite solution that clears the vision to the next step and once an defect is found, retraces back, just to the next line.
  • What else can be a perfect solution than a solved equation with the precise data that is true, just like our scrum delivered, released and deployed solution.
  • The principles of performing an equation is well understood before even starting a scrum team.

If you are interested to know more, you should attend a fundamental training in project management using Scrum by Sathya and Im sure the learning would be knowledgeable and immense as I do.

Note: The example above is taken from: and not my own creation.


Posted by on September 7, 2011 in New forms in Agile


Tags: , , , , ,