“ Can your QA squad handle this? ” When I hear this query, the gears in my head begin to spin. What day is it? Who is available? What is on our home? Do I expect my team to call in sick after the upcoming squad happy hour tomorrow? Whether you are make sprint planning or an impromptu project, if you take a team, then you have to be comfy with Capacity Planning!

Level of Effort (LOE) is Not Duration or Capacity

Let ’ s say you are survey Task 1 with your analyst:

Lead:How long will this task take you to do?Analyst: Two days.

Many people stop here. They have successfully obtained theLevel of Effort (LOE)which they can plug into their plan. But the conversation should continue:

Lead:Are there any dependencies to discharge this chore?Analyst:Yes. When I am halfway do I will take the other analyst to finish Task 2 before I can continue.Lead:I see she will be occupy about a day to finish Task 2. Given that, it looks like it will be 3 days to complete the employment from start to finish.

Now you feature theDuration. The remain enquiry is: Do you have theCapacity?

Understand the Team ’ s Obligations

I once had a conversation with a squad I had simply joined. They were kvetch about being overworked, and more being piled on. This was preventing them from doing normal dash activities, such as reviewing chore for the upcoming sprints. We decided the best way to prove this to direction was to name all of the tasks they were creditworthy for on a regular basis, and approximate how much time it was taking from their capacity to take on new employment. We see the pursuit:

• Sprint Meetings- The team (a QA team) was responsible for supporting different scrum teams, each with their own set of meetings. A 15-minute meeting way at least 30 min of your time if you take the time to relieve what you are doing, quick-prep for the meeting, and ultimately get your nous back to the original task. Assuming a two-week dash, with 10 daily scrums at 30 minutes each (due to the time lost per meeting), plus four hours of other sprint meetings (planning, audits, closeout), this is about a day and a one-half of lost sprint capacity per person.

• More Meetings!- Every coach has meetings with their team. Company obligations, events, and breeding can too pull the analyst away from sprint labor. It adda up.

  Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

• Bug Verification- As this was a QA team, they had a unceasing stream of bugs be doctor during the sprint. While many were anticipated during the planning, a good number were surpass to the team unexpectedly. We determined that each bug would take an average of an hour to verify, and based on history, we were able to ascertain about how many to look for each sprint.

• Bug Rejects!- This turned out to be our biggest painfulness point. By pulling tag chronicle we discovered a big percentage of bugs went through multiple rounds of rejections. By taking this percentage and multiplying it by the average figure of bugs, we were able to find a more realistic number of bugs the team was reexamine each sprint.

Once we had these basic, easily determined numbers, we be not only able to demonstrate our dearth of Capacity to take on sprint tasks, but we were also able to show the ontogenesis team their impacts to the QA squad with miserable quality. Steps were taken to review bug fixes upstream, which increased the QA team ’ s capacity and morale. Understanding your team ’ s normal obligations, plus accounting for holidays, time off, and the like, gives you a baseline value to subtract from your team ’ s sprint capacity.

Capacity Changes Daily

The hardest thing about capacity is that it literally changes on a daily ground. As you build in the dash, more and more things will impact your team. The capability you had on day one is well-nigh emphatically not the like capacity you get the final few days of the dash:

• Design changes happen, add overhead to the original tasks

• Bugs are found and need aid

• Dependant labor are completed and trigger new task, features are delivered; i.e. everything needs attention at once!

• Priorities vary

• Sh ... stuff occur!

The more sprint you plan for, the more it will become second nature to understand the capability impact.

Account for the Intangibles

Every team has strengths and impuissance. You have your starter and your guru. You should account for this not only for your own team, but any early team forthwith impacting your project. Have a new designer? You might need to provide dependent matter expertise while he get up to speed. New developer? Expect more bugs. Trust your gut instincts. A simple way to account for these and former influences is to apply a multiplier against your final content. In my radical, we just take 6-hour days when planning. This equate to a 25 % multiplier. So if you begin with a 10-day dash, times 25 %, you are starting with 8 day of capacity before you even start. Figure out what act best for you.

Conclusion

Knowing your squad ’ s capacity is critical to planning. Combine this with LOE and duration, and sprint preparation can become routine.Joe Nolan is the Mobile QA team lead at Blackboard. He has over 10 years experience leading multinationally located QA teams, and is the founder of the DC Software QA and Testing Meetup.