Software Engineering Subject code:16CS301
B.Tech III Year – I semester
UNIT I
Agile scrum &Unified process
Session III
S.NYAMATHULLA
ASSISTANT PROFESSOR
DEPARTMENT OF INFORMATION TEHCNOLOGY
AGENDA/OBJECTIVES
Prerequisite of SCRUM Model
History of SCRUM &Unified Process
SCRUM Principles
SCRUM SPRINT STRUCTURE
UNIFIED PROCESS
Conclusion
PREREQUISITE OF SCRUM
What is AGILE
Characteristics of AGILE
AGILE Practices
AGILE Values and Principles
HISTORY OF SCRUM
Scrum is an agile software development by Jeff Sutherland and his
development team 1990s.
Schwaber and Beedle .
SCRUM PRINCIPLES
• The following framework activities: requirements,
analysis, design, evolution, and delivery.
• Work tasks occur within a process pattern called a
sprint. The work conducted within a sprint
• The number of sprints required for each framework
activity will vary depending on product complexity
and size
SCRUM WORKFLOW
•Divide the project into little parts.
•Develop each part in 2-4 weeks.
•During those 2-4 weeks have a meeting every day.
•Use visual aids to motivate the development process.
SCRUM WORKFLOW
•Scrum focuses on developing the product in a series of fixed-length iterations called sprints (usually 2-4 weeks).
•This give teams a framework for shipping software on a regular rhythm.
•Milestones – i.e., the end of a sprint – .
SCRUM WORKFLOW
• SCRUM
SCRUM SPRINT STRUCTURE
Scrum calls for four ceremonies that bring structure to each sprint
Sprint planning: A team planning meeting that determines what to
complete in the coming sprint.
Daily stand-up: Also known as a Daily Scrum, a 15- minute mini-
meeting for the software team to sync.
Sprint demo: A sharing meeting where the team shows what
they've shipped in that sprint.
Sprint retrospective: A review of what did and didn't go well with
actions to make the next sprint better.
SCRUM SPRINT STRUCTURE
• During a sprint, visual artifacts like task boards and
burndown charts, visible to the team and spectators
alike, are powerful motivators.
SCRUM SPRINT STRUCTURE
TASKS BOARD
SCRUM SPRINT STRUCTURE
Burndown charts
SCRUM SPRINT STRUCTURE
• A scrum team has a slightly different composition
than a traditional waterfall project, with three
specific roles:
–product owner,
–scrum master, and
–the development team.
SCRUM SPRINT STRUCTURE
The Product Owner:
–Creates a prioritized wish list called a product backlog
–Closely partners with the business and the team to
ensure
everyone understands the work items in the product backlog
–Gives the team clear guidance on which features to deliver
next
–Decides when to ship the product with a preference
towards more frequent delivery
SCRUM SPRINT STRUCTURE
The Project Owner
• This is a role has to be done by a single individual who
bring a single unified view to the project.
• This role is not the same as a project manager.
• The Project Owner ensures that the development team
delivers the most value to the business.
SCRUM SPRINT STRUCTURE
SCRUM MASTER
• The Scrum Master is the champion for scrum.
• They coach the team, the product owner.
• An effective scrum master deeply understands the
work being done by the team and can help the team
optimize their delivery flow.
• They schedule the needed resources for sprint planning,
stand- up, sprint review, and the sprint retrospective.
SCRUM SPRINT STRUCTURE
SCRUM tEAM
• The Scrum Team controls its own destiny and self-organizes
around their work.
• Agile teams use pull models where the team pulls a certain
amount of work off the backlog and commits to completing it
that sprint, which is very effective in maintaining quality and
ensuring optimum performance of the team over the long-term.
INTERESTING
• The Scrum team need to create their own
• Definition of Done
• – A programmer might call something done when the code has been
written. The tester might think that done means that all of the tests
have passed. A business person may think that done means we can
now sell it to customers, and it's ready for them to use.
INTERESTING
• The Scrum Guide was written and is maintained by the
creators of Scrum, Ken Schwaber and Jeff Sutherland and is
considered as the Body of Knowledge for Scrum.
• http://www.scrumguides.org
AGILE UNIFIED PROCESS
• What is Unified Process ??
• Unified process (UP) is an architecture-centric, use-case driven,
iterative and incremental development process that leverages
unified modeling language and is combined with the system process
engineering metamodel.
AGILE UNIFIED PROCESS
-The leading object-oriented methodology for the development
of large-scale software
-Maps out when and how to use the various UML techniques
-Develop high-risk elements in early iterations
-Deliver value to customer
AGILE UNIFIED PROCESS
-The Unified Process is an adaptable methodology.
-The Unified Process is a modeling technique.
• UML stands for unified modeling language.
-The object-oriented paradigm is iterative and incremental in
nature
UNIFIED PROCESS PHASES
-Inception
Establish the business case for the system,
define risks, obtain 10% of the requirements,
estimate next phase effort.
-Elaboration
Develop an understanding of the problem
domain and the system architecture,
risk significant portionsmay be coded/tested,
80% major requirements identified.
UNIFIED PROCESS PHASES
Construction
System design, programming and testing.
Building the remaining system in short iterations.
TRAnsition
Starts when beta testing is completed,
Deploy the system in its operating environment.
Deliver releases for feedback and deployment
AGILE UNIFIED PROCESS
-
THE PHASES/WORKFLOWS OF
UNIFIED PROCESS
NOTE: Most of the requirements work or workflow is done in the
inception phase. However some is done later.
THE PHASES/WORKFLOWS OF
UNIFIED PROCESS
NOTE: Most of the requirements work or workflow is done in the
Construction phase. However some is done later.
CONCLUSION
History of SCRUM
SCRUM Principles
SCRUM SPRINT STRUCTURE
Unified Process
NEXT SESSION
IMPLEMENTATION OF AGILE MODELS
Requirement Engineering
