Introduction
Scrum methodology defines an agile software improvement protocol which functions as a project management cover around present engineering applies to iteratively and incrementally grow software. The paper was a Scrum process was published by Laurie Williams, Gabe Brown, and Nachiappan Nagappan in the year 2011. Laurie Williams was originally teaching at the State University of North Carolina while the other authors were from the Microsoft Corporation. Any developer who is interested in getting credit for his or her duty while using scrum, he or she should be in a position to demonstrate the original functionality delivered by a feature at the close of every short reiteration during an iteration evaluation session (Williams et al. 3). Such as short duration focus without the existence of the checks and stabilities of sound engineering applies may result to a team to disregard quality. The presented article offers the experiences of the three classes at Microsoft applying Scrum with an added nine sound engineering practices.
Flaccid Scrum defines the utilization of the management project of the scrum but without the application of the prescribed practices of engineering. This, therefore, slows down the progress of the progress via iterations as a result of the lack of devotion to the quality of code manufactured at the sprints (Williams et al. 4). Normally, the features created from the prints originate from the easiest situation referred to as the "happy path" which encounters the criteria. This, therefore, tags the feature as complete, and the sprint iteration carries on to the next piece despite the last feature being not completely fully. The prevention of the flaccid scrums can be conducted through the addition of the engineering practices to the scrum procedures.
Planning poker is one of the major engineering practices that is carried out by the Microsoft group. Planning poker is implemented by the team to estimate every individual hour to make a completion of the within the iteration. In the current years, some of the supple software have assessed the effort that is needed to make a completion of the necessities selected to be applied in a sprint through a wideband which is known as palling poker. The integration practice has been continuously applied by the Microsoft team in the article. In other words, the continuous integration practice where the people involved in the work to construct the main system. Every developer has been presented to make an integration on a daily basis. Another important engineering practice that is applied by the Microsoft team is the basic scrum (Williams et al. 4). This practices offered a huge description of the process applied to make the integration work complete. Lastly code coverage also makes part of the imperative engineering practices applied by the Microsoft team in the article.
Conclusion
The authors base their conclusion on the achievements which they have acquired through the engineering practices which become of importance for more education. Therefore when making a summary of the article one of the most significant point that is to be determined is the importance of the engineering practices.
Work Cited
Williams, Laurie, et al. "Scrum+ engineering practices: Experiences of three Microsoft teams." Empirical Software Engineering and Measurement (ESEM), 2011 International Symposium on. IEEE, 2011.
Cite this page
Scrum Process Article Analysis Essay. (2022, Jun 23). Retrieved from https://proessays.net/essays/scrum-process-article-analysis-essay
If you are the original author of this essay and no longer wish to have it published on the ProEssays website, please click below to request its removal:
- Lego Marketing Strategy Analysis Research Paper
- Communication With Stakeholder's Essay
- Leadership Interview Analysis Paper Example
- Pat Brown: Father of Modern California Essay Example
- Research Paper on Management and Leadership Theories
- Essay on Body Safety Education: Essential for Schools to Protect Children from Sexual Abuse
- Essay Example on Leadership: Striking a Balance of Inclusivity in the Workplace