Webinar Replay Now Available: Shifting to Agile Methods - The Keys for Long-Term Success
If you were unable to attend our webinar, Shifting to Agile Methods - The Keys for Long-Term Success, a replay is now available.
Changes to the software development process, such as moving toward Agile methods, must demonstrate sustainable results over time versus just short-term wins. There are two keys to reaching long-term success that should be considered up front – the new process must be repeatable and measurable.
In this session, AccuRev’s Chris Lucca and QSM’s Larry Putnam, Jr. explore these two keys to success.
Specifically, they cover:
Part III: Finding the Optimal Team Size for Your Project
In part one of our team size series, we looked at Best and Worst in Class software projects and found that using small teams is a best practice for top performing projects. Part two looked at differences in cost and quality between small and large team projects and found that small teams use dramatically less effort and create fewer defects. But simply knowing that small teams perform better doesn’t tell us how small a team to use. Most software metrics scale with project size, and team size is no exception. Management priorities must also be taken into account.
Tuning Effort for Best in Class Analysis and Design
After reading Best Projects/Worst Projects in the QSM IT Almanac, a SLIM-Estimate® user noted that the Best in Class Projects expended around 28% of their total project effort in analysis and design (SLIM Phase II) compared to 10% for the Worst in Class Projects. She wanted to know how she could tune her SLIM-Estimate templates to build in the typical best in class standard for Analysis and Design.
In SLIM-Estimate, effort and duration for phases I and II are calculated as a percentage of Phase III time and effort. To create a template for estimating phases II and III that will automatically allocate 28% of total project effort to analysis and design (Phase II), follow these simple steps.
