Of all Agile frameworks, scrum is the most popular one. Scrum methodology is highly
recommended for developing IT projects and it is so widely recommended for it that it is often
confused with Extreme Programming or “XP” Agile framework, which is synonymous with
software development. Both the frameworks are much similar, and to a person not
conversant with Agile, both might appear to be the same at a first glance. While most
Agile processes and events remain the same, there are some subtle differences between
the two frameworks.
recommended for developing IT projects and it is so widely recommended for it that it is often
confused with Extreme Programming or “XP” Agile framework, which is synonymous with
software development. Both the frameworks are much similar, and to a person not
conversant with Agile, both might appear to be the same at a first glance. While most
Agile processes and events remain the same, there are some subtle differences between
the two frameworks.
Sprint durations
Typically, in scrum, the sprint iteration can last from two weeks up to one month. In XP,
the duration is much shorter, and generally lasts from one to two weeks. The sprint
duration does not exceed two weeks in XP.
Typically, in scrum, the sprint iteration can last from two weeks up to one month. In XP,
the duration is much shorter, and generally lasts from one to two weeks. The sprint
duration does not exceed two weeks in XP.
Committing the sprint backlog
One of the major differences, and an important one too, is how user stories are
committed in the sprint backlog while implementing scrum and XP. In scrum, the sprint
backlog is “owned” by the development team. Once the team accepts the sprint backlog,
all the user stories in the backlog are “committed” for development purposes. The team
is required to complete all the user stories stated in the backlog. Moreover, once
committed, the sprint backlog cannot be “changed” while implementing scrum. If any
new user story is required to be developed, it can only be included in the next sprint after
a new sprint planning meeting is conducted. This is not the case with XP. The sprint
backlog does not become “static” even after it is accepted by the team and the user
stories are taken up for development. If required, based upon the feedback received
from the stakeholders, a user story taken up for development can be replaced with a
nother one having the same estimation in terms of story points. Therefore, the sprint
backlog is not “committed” at any time in XP. New stories can be replaced in lieu of
those currently existing in the backlog – something that is impossible in scrum. However,
it is important to know that such a “replacement” of user story is only possible in XP
before the particular user story is taken up for execution in the daily sprint. Once the
development of a user story starts in XP, it cannot be replaced. Read more at http://goo.gl/35Yq67
One of the major differences, and an important one too, is how user stories are
committed in the sprint backlog while implementing scrum and XP. In scrum, the sprint
backlog is “owned” by the development team. Once the team accepts the sprint backlog,
all the user stories in the backlog are “committed” for development purposes. The team
is required to complete all the user stories stated in the backlog. Moreover, once
committed, the sprint backlog cannot be “changed” while implementing scrum. If any
new user story is required to be developed, it can only be included in the next sprint after
a new sprint planning meeting is conducted. This is not the case with XP. The sprint
backlog does not become “static” even after it is accepted by the team and the user
stories are taken up for development. If required, based upon the feedback received
from the stakeholders, a user story taken up for development can be replaced with a
nother one having the same estimation in terms of story points. Therefore, the sprint
backlog is not “committed” at any time in XP. New stories can be replaced in lieu of
those currently existing in the backlog – something that is impossible in scrum. However,
it is important to know that such a “replacement” of user story is only possible in XP
before the particular user story is taken up for execution in the daily sprint. Once the
development of a user story starts in XP, it cannot be replaced. Read more at http://goo.gl/35Yq67
