CUI, WAH

Assignmnent_02

Topic: Scrum and XP

Submitted From:
Name: Muhammad Umair
Reg No: FA18-BSE-3B-088

Submitted To:
Ms.Ayesha Hussain

Date: Oct 16,2019

1
What is Scrum?
Scrum is one of the implementations of agile methodology. In which incremental builds are delivered to
the customer in every two three-week time.

Example :
We have an example from social media as episodic story way. Which have many cast of
characters and a simple fictional product in the form of episodes of a single drama. Having
many episodes with a lot of information and advices to handle any situation. In this scrum
master would be a part of story or not it depend on scrum master his self. Characters work as a
team members of drama, which will be explain in sprints. Product Owner is a Director of drama.
⮚ Scrum
The above scenario shows the agile methodology of all members in dramatic session. Because of
daily based meetings, shootings, having all members of involved in drama.
⮚ Scrum Roles
● Scrum Master
Scrum Master is basically a member of team who handle each and every thing properly in a
very good management. In this example Scrum Master would be a Director of
drama but it is not mandatory. Actually director is a person who manage all system
in drama start to end.
● Team
Meetings are held in a single room called Team Room. Having all members of team.
Team including following members;
▪ Director of Drama (ScrumMaster or/and Product Owner)
▪ Characters involved in Drama Serial
▪ Developers

2
 ▪ Designers
▪ QA Testers (Quality Assurance)
▪ Camera Man’s
▪ Staff
● Product Owner
Product Owner is a member or Customer who demanded to develop a software. After
completion of software send to the product owner. But in this also Director of a
drama will be a Product Owner because if director his self wants to release a drama.
So in this way Director will be a Product Owner
⮚ Scrum Artifacts
● Product Backlog
In this all currently given requirements for the project e.g. Drama Serial there are many
episodes in a single drama. So all stories requirements of drama are called Product
Backlog.
● Sprint Backlog
Episodes are divided, let suppose there are total 10-Episodes in drama serial. Each episode is
known as Sprint. So there are 10 Sprint i.e. sprint-1, sprint-2, …, sprint-10.
● Sprint Burndown
In this the separated sprints are developed in the form story cards. Now its time to start
work on drama serial as a sprint manner. First, we have to develop 1st Sprint and
tested, designed and finally send to product owner as a single output of product
backlog, and so on.
● Burn Down Chart
The burn down chart shows all work done in the regular days or in a week and so on. Each
and every step work done should have to show on burn chart. As show in figure.

What is XP?
XP means “Extreme Programming”. XP is a set of engineering practices which are adopted in whole or in
part by software development teams and organizations – to create reliable software products.

Explanation:
Like other agile methodologies, extreme programming aims to cope easily with changing requirements.
However, it's advantage is that it is developed to create products faster.

Both the customer and the development team are committed and equally involved in the project life
cycle. The golden rule of XP is test first, then develop. Of course, there are risks when you go to
“extreme” testing and then coding. However, this approach is highly efficient, and that is why it is widely

3
used in software development.

Example: Developing a game

Problem Statement: A client requires a game to be developed from scratch.

Actors: Customer, Developers, Tracker Regular Flow of Events:

1. The customer gives requirements, time and budget.

2. The developers start programming.

3. The QA team tests the game modules.

4. The customer has more requirements.

5. The cycle repeats.

Using XP:

1. Face to face meeting is called involving the customer and developers.

2. The customer defines requirements, the budget and the timeline in the form of a story (game
modules).

3. The Project Manager becomes the Tracker and tracks the game development progress.

4
4. The development team starts working in pairs. The code for different modules is written and
debugged at the same time.

5. Each week a meeting is held to discuss the progress. The customer can define new requirements.

6. Every quarter a meeting is held to discuss the status of the stories.

7. After old stories are completed i.e. high priority modules are finished, a new set of stories are formed
(requirements for the next quarter).

References: -

https://agilepainrelief.com/notesfromatooluser/2018/08/scrum-by-example.html

https://www.google.com/search?q=QA+tsters&oq=QA+tsters&aqs=chrome..69i57j0l5.3036j0j7&sourcei
d=chrome&ie=UTF-8

https://www.geeksforgeeks.org/software-engineering-extreme-programming-xp/