preview

This Paper Was Written As A Study By Laurie Williams Of

Decent Essays
Open Document

This paper was written as a study by Laurie Williams of North Carolina State University, where she tracked three development teams from Microsoft. Gabe Brown, Adam Meltzer, Nachiappan Nagappan serve a coauthors and are representatives from Microsoft. Flaccid Scrum refers to a development team that only prescribes to Scrum practices and neglects to adopt important engineering practices. Production for these teams will eventually slow down, since their lack of engineering practices leads teams to pay little attention to code quality. Without proper engineering practices, these Flaccid Scrum teams usually only implement the easiest features of the product, which leads to a larger backlog and longer release timeline. The authors provide nine …show more content…

Again the downside to this practice is a further investment in time. The third practice i will mention is Code coverage. Microsoft recommends that unit test should have around 80% code coverage, and teams that achieve this level of coverage reported less error and more productivity over the long run. The team felt that managing coverage was helpful for finding dead code and areas that needed better testing, yet writing so many unit tests would often lead to a long amount of time debugging and fixing code to pass the unit test. Finally the fourth engineering practice I would like to discuss is Planning poker. I was very surprised to hear the author report that teams who used the planning poker strategy saw a significantly lower estimation error than teams that did not use the practice. However the teams noted that planning poker required a significant amount of time and more upfront work, before release planning could begin. The authors of this paper tracked three development teams at Microsoft over the course of 11 to 18 months. Each team varied inside and in project content yet each team was a working on their first release. All teams utilized the Scrum methodologies as well as Microsoft 's engineering best practices. The authors collected several data point during the team 's development. These data points described and covered both scrum

Get Access
Related
Get Access