• .NET Testing & ALM

    Top 4 Challenges for Agile Planning

    Despite trying to achieve simplicity, Agile teams may still run across difficult issues. In this section some of the more common challenges are explored. HANDLING INCOMPLETE WORK AT THE END OF AN ITERATION It is not uncommon for a team to have incomplete work at the end of an iteration. Unfinished work is an important issue to identify as it signals a potential problem with one or more aspects of the team. When an iteration is planned, the team sets an expectation with the customer. When those expectations are not met, the customer could lose faith in the team’s ability ...
    October 09, 2013
  • .NET Testing & ALM

    [A Few Tips] How to Decompose User Stories and Assign Tasks

    Decomposition into Tasks Your backlog is normally comprised of requirements in the form of User Stories which depict the resulting value required by the users of the system. During iteration planning, teams take the highest value requirements and assign them to the current or next iteration, filling the iteration to capacity. Agile teams typically do not decompose requirements into work tasks until they are assigned to an iteration. Agile teams spend the first few hours of each iteration going through iteration planning, and a part of that process is the decomposition of requirements into work that can be completed by ...
    October 03, 2013
  • .NET Testing & ALM

    The Importance of Measuring Iteration Velocity and Capacity for Agile Planning

    When iteratively planning an Agile project where the team partitions work into timeboxed iterations, understanding capacity is very important. Planning an iteration is very much like using a bucket to scoop water out of a pool, where the pool represents the complete set of backlog items on your project and the bucket represents the amount of work that can be accomplished in a single iteration. Understanding how much water a bucket holds will give you an idea of how many buckets are required to empty the pool. Similarly, understanding how much work your team can deliver in an iteration will ...
    September 25, 2013
  • .NET Testing & ALM

    The Importance of Prioritizing and Sizing Your Backlog for Agile Planning

    Prioritized and Sized Backlog For agile planning to work, you must have a prioritized and sized (estimated) backlog. A prioritized backlog is simply a list of work that needs to get done that is ordered by priority. Essentially, the work at the top of the list is the most important and should be done first. In many cases, customers have a difficult time prioritizing lists of features, however, this makes the prioritized backlog even more important to produce. Another requirement of this backlog is that each of the items must be sized, which is another way of saying that the ...
    September 18, 2013
  • .NET Testing & ALM

    3 plus 1 Awesome Features in TeamPulse You Probably Don’t Know About

    In the last release we made some major improvements in TeamPulse so it can provide smoother experience on mobile devices. Now it’s even easier to track your work from your iPad or your smartphone. TeamPulse on your tablet We have done a lot of performance and UX improvements for mobile device. As a result you now got a faster board and list view, better search, quick add and activity stream, and more. While you would experience those for yourself, we wanted to share with you some tips and tricks on how to make your life easier when working with TeamPulse ...
    September 17, 2013