Scrum/Scrum_baseline_EN/exported_HTML/Scrum/guidances/concepts/what_is_scrum.html - gerrit/epf/org.eclipse.epf.nl-libraries - Git at Google

 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
 <!-- VERSION rmc:7.1.0 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
 <!-- START NON-TRANSLATABLE -->
 <title>Scrum&amp;#92;guidances&amp;#92;concepts&amp;#92;&amp;#92;what_is_scrum.xmi</title>
 </head>
 <!-- WARNING: do not modify the generated comments in this file below this line.  They are used as markers for the import process. -->
 <body>
 Element Name: what_is_scrum.xmi<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: presentationName<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:presentationName,_3WivIBTQEduFIr9xNbwGyQ CRC: 63609431 -->What's Scrum<!-- END:presentationName,_3WivIBTQEduFIr9xNbwGyQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: briefDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:briefDescription,_3WivIBTQEduFIr9xNbwGyQ CRC: 296343939 -->Scrum is a project management technique leading to the release of a product with the highest possible business value in the smallest amount of time.<!-- END:briefDescription,_3WivIBTQEduFIr9xNbwGyQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: mainDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:mainDescription,-MSO8KF-0IlKZJGnSwwTNZA CRC: 2335804464 --><p>
     Scrum is a thin and iterative project management process, which belongs to the <a title="Agile method" href="http://en.wikipedia.org/wiki/Agile_software_development">Agile methods</a> family, sharing the values defined in
     the Agile manifesto and applying its fundamental principles.
 </p>
 <h5>
     Summary
 </h5>
 <p>
     Here's a summary of Scrum:
 </p>
 <p class="quote">
     Scrum leads to oftenly and regulary showing (every 2 or 4 weeks, depending on <a class="elementLink" href="./../../../Scrum/guidances/termdefinitions/sprint_494C0C24.html" guid="_kftWoIHqEduFs9jH8xc4xw">Sprint</a>
     length) a working (partial) product. Business analysis identifies requirements and defines their priorities. Team gets
     organized in order to determine the best way to implement most prioritized requirements. At the end of each Sprint,
     everybody can see the actual product working and contribute to make a decision on what's next: either release it as is,
     or continue to improve it through an additional sprint before reconsidering again.
 </p>
 <h5>
     Origin
 </h5>
 <p>
     Scrum is a term from rugby. The process revolves around a strong team looking forward to reaching a goal, as it is the
     case with rugby when a pack deploys its collective strength to move forward witht the ball during a scrum.
 </p>
 <p>
     Scrum particulary focuses on the social and collective aspect of development. Scrum Goal is to improve quality and
     productivity, with an empirical approach, relying on autonomous teaming.
 </p>
 <h5>
     Empirism
 </h5>
 <p>
     An empirical process, thus experience-based, requires a good visibility, frequent inspections and adaptation to
     planning changes. This is applied in Scrum through the 2 regulation cycles:
 </p>
 <ul>
     <li>
         During Daily Scrums, passed day experience is taken into account to adapt the planning for remaining days in the
         sprint.
     </li>
     <li>
         During sprint reviews, passed sprint experience is taken into account to adapt the release planning regarding next
         sprints.
     </li>
 </ul>
 <p>
     Sprint tasks are not defined very precisely: no start date, no end date, no dependency. Scrum considers that it's not
     predictable. Scrum empirism continuously relies on current project state analysis for process control and risk
     reduction.
 </p>
 <h5>
     Scope
 </h5>
 <p>
     Scrum does not describe all the software development activities (analysis, design, coding, testing) and must be
     considered, rather than a full process, more as a process pattern to use for project and requirement management.
     &lt;br0/&gt; Scrum does not provide help to achieve development technical activities. It is Team's job to define by
     itself what's the work to do.
 </p>
 <h5>
     Diffusion
 </h5>
 <p>
     Scrum exists since the 90s and its popularity has been growing for a few years and it has been used by hundreds of
     projects around the world. For 3 years now, a certification process has been set up. In November 2006, more than 7000
     people had obtained ScrumMaster certification.
 </p>
 <p>
     &nbsp;<img height="56" alt="ScrumMaster" src="./resources/csm.jpg" width="179" />
 </p>
 <p>
     For more informations on Scrum, go to<a href="http://en.wikipedia.org/wiki/Scrum_(management)" target="_blank">http://en.wikipedia.org/wiki/Scrum_%28management%29</a>
 </p><!-- END:mainDescription,-MSO8KF-0IlKZJGnSwwTNZA -->
 </body>
 </html>
	<?xml version="1.0" encoding="UTF-8"?>
	<!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
	<!-- VERSION rmc:7.1.0 -->
	<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
	<!-- START NON-TRANSLATABLE -->
	<title>Scrum&#92;guidances&#92;concepts&#92;&#92;what_is_scrum.xmi</title>
	</head>
	<!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. -->
	<body>
	Element Name: what_is_scrum.xmi<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: presentationName<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:presentationName,_3WivIBTQEduFIr9xNbwGyQ CRC: 63609431 -->What's Scrum<!-- END:presentationName,_3WivIBTQEduFIr9xNbwGyQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: briefDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:briefDescription,_3WivIBTQEduFIr9xNbwGyQ CRC: 296343939 -->Scrum is a project management technique leading to the release of a product with the highest possible business value in the smallest amount of time.<!-- END:briefDescription,_3WivIBTQEduFIr9xNbwGyQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: mainDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:mainDescription,-MSO8KF-0IlKZJGnSwwTNZA CRC: 2335804464 --><p>
	Scrum is a thin and iterative project management process, which belongs to the <a title="Agile method" href="http://en.wikipedia.org/wiki/Agile_software_development">Agile methods</a> family, sharing the values defined in
	the Agile manifesto and applying its fundamental principles.
	</p>
	<h5>
	Summary
	</h5>
	<p>
	Here's a summary of Scrum:
	</p>
	<p class="quote">
	Scrum leads to oftenly and regulary showing (every 2 or 4 weeks, depending on <a class="elementLink" href="./../../../Scrum/guidances/termdefinitions/sprint_494C0C24.html" guid="_kftWoIHqEduFs9jH8xc4xw">Sprint</a>
	length) a working (partial) product. Business analysis identifies requirements and defines their priorities. Team gets
	organized in order to determine the best way to implement most prioritized requirements. At the end of each Sprint,
	everybody can see the actual product working and contribute to make a decision on what's next: either release it as is,
	or continue to improve it through an additional sprint before reconsidering again.
	</p>
	<h5>
	Origin
	</h5>
	<p>
	Scrum is a term from rugby. The process revolves around a strong team looking forward to reaching a goal, as it is the
	case with rugby when a pack deploys its collective strength to move forward witht the ball during a scrum.
	</p>
	<p>
	Scrum particulary focuses on the social and collective aspect of development. Scrum Goal is to improve quality and
	productivity, with an empirical approach, relying on autonomous teaming.
	</p>
	<h5>
	Empirism
	</h5>
	<p>
	An empirical process, thus experience-based, requires a good visibility, frequent inspections and adaptation to
	planning changes. This is applied in Scrum through the 2 regulation cycles:
	</p>
	<ul>
	<li>
	During Daily Scrums, passed day experience is taken into account to adapt the planning for remaining days in the
	sprint.
	</li>
	<li>
	During sprint reviews, passed sprint experience is taken into account to adapt the release planning regarding next
	sprints.
	</li>
	</ul>
	<p>
	Sprint tasks are not defined very precisely: no start date, no end date, no dependency. Scrum considers that it's not
	predictable. Scrum empirism continuously relies on current project state analysis for process control and risk
	reduction.
	</p>
	<h5>
	Scope
	</h5>
	<p>
	Scrum does not describe all the software development activities (analysis, design, coding, testing) and must be
	considered, rather than a full process, more as a process pattern to use for project and requirement management.
	<br0/> Scrum does not provide help to achieve development technical activities. It is Team's job to define by
	itself what's the work to do.
	</p>
	<h5>
	Diffusion
	</h5>
	<p>
	Scrum exists since the 90s and its popularity has been growing for a few years and it has been used by hundreds of
	projects around the world. For 3 years now, a certification process has been set up. In November 2006, more than 7000
	people had obtained ScrumMaster certification.
	</p>
	<p>
	<img height="56" alt="ScrumMaster" src="./resources/csm.jpg" width="179" />
	</p>
	<p>
	For more informations on Scrum, go to<a href="http://en.wikipedia.org/wiki/Scrum_(management)" target="_blank">http://en.wikipedia.org/wiki/Scrum_%28management%29</a>
	</p><!-- END:mainDescription,-MSO8KF-0IlKZJGnSwwTNZA -->
	</body>
	</html>