<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://develop.consumerium.org/w/index.php?action=history&amp;feed=atom&amp;title=Scrum</id>
	<title>Scrum - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://develop.consumerium.org/w/index.php?action=history&amp;feed=atom&amp;title=Scrum"/>
	<link rel="alternate" type="text/html" href="https://develop.consumerium.org/w/index.php?title=Scrum&amp;action=history"/>
	<updated>2026-05-04T09:59:52Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.6</generator>
	<entry>
		<id>https://develop.consumerium.org/w/index.php?title=Scrum&amp;diff=14486&amp;oldid=prev</id>
		<title>142.177.104.110 at 04:00, 22 February 2004</title>
		<link rel="alternate" type="text/html" href="https://develop.consumerium.org/w/index.php?title=Scrum&amp;diff=14486&amp;oldid=prev"/>
		<updated>2004-02-22T04:00:42Z</updated>

		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;A &amp;#039;&amp;#039;&amp;#039;scrum&amp;#039;&amp;#039;&amp;#039; is an iterative, incremental process for developing software in chaotic environments.  Scrum consists of a series of [[30 day sprint]]s, each sprint producing an executable. Between sprints, all interested parties evaluate progress and reevaluate technical and business requirements. Work is reestablished and the team enters into another sprint.  &amp;#039;&amp;#039;There are other agile methodologies that rely on a [[14 day sprint]] or up to a [[90 day sprint]].&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
The &amp;#039;&amp;#039;&amp;#039;scrum master&amp;#039;&amp;#039;&amp;#039; holds the daily &amp;#039;&amp;#039;&amp;#039;scrum meeting&amp;#039;&amp;#039;&amp;#039; to make sure everyone is unblocked, check progress, and determine what is preventing more progress.  It is a short meeting, never more than 30 minutes, and is restricted to getting commitments for the next day, and what has blocked commitment for the previous.&lt;br /&gt;
&lt;br /&gt;
Followup meetings can be scheduled to deal with the issues identified, and these have of course can use another [[meeting style]].  An advantage of immediate followup is that everyone required for it has just come out of the scrum, and so is available immediately.&lt;br /&gt;
&lt;br /&gt;
It is basic to the scrum process that everyone be available for that 30 minute meeting.  It is not clear how well these methods work with [[telework]] or any very distributed project.&lt;br /&gt;
&lt;br /&gt;
[http://www.scrumalliance.org/start_rules.php The Scrum Alliance] certifies their &amp;quot;scrum masters&amp;quot; as being able to conduct these meetings the right way.&lt;/div&gt;</summary>
		<author><name>142.177.104.110</name></author>
	</entry>
</feed>