Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

AGILE METHODOLOGY SCRUM AND XP, Exams of Computer Science

BEST NOTES FOR EXAMINATION MAJOR PART

Typology: Exams

2016/2017

Uploaded on 12/13/2017

aabid-wani-1
aabid-wani-1 🇮🇳

1 document

1 / 5

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
What is Agile Methodology?
AGILE methodology is a practice that
promotes continuous iteration of development and
testing throughout the software development lifecycle
of the project. Both development and testing activities
are concurrent unlike the Waterfall model.
The agile software development emphasizes on four
core values.
1. Individual and team interactions over processes
and tools
2. Working software over comprehensive
documentation
3. Customer collaboration over contract negotiation
4. Responding to change over following a plan
Scrum
SCRUM is an agile development method which
concentrates specifically on how to manage tasks
within a team-based development environment.
Basically, Scrum is derived from activity that
occurs during a rugby match. Scrum believes in
empowering the development team and
advocates working in small teams (say- 7 to 9
members). It consists of three roles, and their
responsibilities are explained as follows:
1. Scrum Master
pf3
pf4
pf5

Partial preview of the text

Download AGILE METHODOLOGY SCRUM AND XP and more Exams Computer Science in PDF only on Docsity!

What is Agile Methodology?

AGILE methodology is a practice that promotes continuous iteration of development and testing throughout the software development lifecycle of the project. Both development and testing activities are concurrent unlike the Waterfall model. The agile software development emphasizes on four core values.

  1. Individual and team interactions over processes and tools
  2. Working software over comprehensive documentation
  3. Customer collaboration over contract negotiation
  4. Responding to change over following a plan

Scrum

SCRUM is an agile development method which concentrates specifically on how to manage tasks within a team-based development environment. Basically, Scrum is derived from activity that occurs during a rugby match. Scrum believes in empowering the development team and advocates working in small teams (say- 7 to 9 members). It consists of three roles, and their responsibilities are explained as follows:

  1. Scrum Master

Master is responsible for setting up the team, sprint meeting and removes obstacles to progress

  1. Product owner The Product Owner creates product backlog, prioritizes the backlog and is responsible for the delivery of the functionality at each iteration
  2. Scrum Team Team manages its own work and organizes the work to complete the sprint or cycle

Process flow of Scrum Methodologies:

Process flow of scrum testing is as follows:

  • Each iteration of a scrum is known as Sprint
  • Product backlog is a list where all details are entered to get end product
  • During each Sprint, top items of Product backlog are selected and turned into Sprint backlog
  • Team works on the defined sprint backlog
  • Team checks for the daily work
  • At the end of the sprint, team delivers product functionality.

eXtreme Programming (XP) Extreme

Programming technique is very helpful when there is constantly changing demands or requirements from the customers or when they are not sure about

In this type of methodology, releases are based on the shorter cycles called Iterations with span of 14 days time period. Each iteration includes phases like coding, unit testing and system testing where at each phase some minor or major functionality will be built in the application.

Phases of eXtreme programming:

There are 6 phases available in Agile XP method, and those are explained as follows:

Planning

  • Identification of stakeholders and sponsors
  • Infrastructure Requirements
  • Security related information and gathering
  • Service Level Agreements and its conditions

Analysis

  • Capturing of Stories in Parking lot
  • Prioritize stories in Parking lot
  • Scrubbing of stories for estimation
  • Define Iteration SPAN(Time)
  • Resource planning for both Development and QA teams

Design

  • Break down of tasks
  • Test Scenario preparation for each task
  • Regression Automation Framework

Execution

  • Coding
  • Unit Testing
  • Execution of Manual test scenarios
  • Defect Report generation
  • Conversion of Manual to Automation regression test cases
  • Mid Iteration review
  • End of Iteration review

Wrapping

  • Small Releases
  • Regression Testing
  • Demos and reviews
  • Develop new stories based on the need
  • Process Improvements based on end of iteration review comments

Closure

  • Pilot Launch
  • Training
  • Production Launch
  • SLA Guarantee assurance
  • Review SOA strategy
  • Production Support