SE-3

Question 1

Agile development

Answer 1

➢ Set of methods & methodologies
➢ Made up of a number of good practices
➢ Help a team think & work more
efficiently.

Question 2

Benefits of agile

Answer 2

Deliver on time & budget
Deliver a high-quality product
Deliver a maintainable code
Make the client happy
Work happy

Question 3

Agile Manifesto

Answer 3

1. Individuals & interactions over process & tools
2. Working software over comprehensive documentation
3. Customer collaboration over contract negotiation
4. Responding to change over following a plan

Question 4

Agile principles

Answer 4

early release of the developing
product to the customer.
▪ Getting rapid feedback from the
customer & incorporating that feedback
into new design experiments.

Question 5

Agile software development life cycle

Answer 5

1. Plan
   2.Design
   3.Develop
   4.Test
   5.Deploy
   6.Review
   7.Launch

Question 6

1.Agile:Requirement Gathering

Answer 6

Define the requirements.
▪ The features your application will provide
▪ Should explain business opportunities

Features of good requirements
➢ Clear
➢ Unambiguous/obvious
➢ Consistent
➢ Prioritised

Question 7

Agile:. Design the requirements

Answer 7

to show the work of new features and show how it will
apply to your existing system.

Question 8

Agile: Develop/ iteration:

Answer 8

start working on their project,
which aims to deploy a working product.

Question 9

Agile: Testing

Answer 9

Quality Assurance team examines the product’s
performance and looks for the bug

Question 10

Agile: Deployment

Answer 10

issues a product for the user’s work
environment.

Question 11

Agile: Feedback/Review

Answer 11

team receives feedback about the product and
works through the feedback.

Question 12

Agile methodologies

Answer 12

scrum

Question 13

Scrum Process

Answer 13

an agile project management framework
that helps teams structure and manage their work
through a set of values, principles, and practices.

Question 14

Sprint

Answer 14

break work into
goals to be completed within time-boxed
iterations, called sprints.

Question 15

Sprint

Answer 15

Target duration is 1-4 weeks
Team can seek outside advice, help, information, support
* Only the Product Owner has the authority to cancel the
Sprint
* No changes during the sprint.

Question 16

Kanban board

Answer 16

Arrangement of columns to track work progress
Each column represents a step in the development process

Easy to identify progress and bottlenecks

Question 17

Burn Down Chart

Answer 17

Updated before every Daily Standup Meeting
Scrum Master adds up the estimated hours for all
remaining tasks on the Kanban board

Question 18

Scrum Artifacts

Answer 18

• Product backlog
• Sprint backlog
• Increment

Question 19

Product backlog

Answer 19

Includes Requirements for the system or product being
developed
* Product owner is responsible for the contents,
prioritization and availability of product backlog

Question 20

Sprint backlog

Answer 20

Set of Product Backlog items selected for the Sprint

Plan for delivering the product Increment and realizing
the Sprint Goal.

Question 21

Increment

Answer 21

Scrum requires team to build increment/slice of the
product of functionality
* Definition of ‘Done’

Question 22

The scrum team

Answer 22

–Product Owner
–Scrum Master
– Development Team

Question 23

Scrum Master

Answer 23

Responsible for ensuring Scrum is understood and
enacted

servant-leader for the Scrum Team.

filled by a Project Manager or Dev Team
Member

to remove impediments/ obstacles

Question 24

Product owner

Answer 24

Responsible for representing the interests of everyone
with the stake for the project
* Managing the product backlog in priority order
* they must deeply understand the customer/end-user need

Question 25

Development team

Answer 25

• Responsible for developing the functionality
• Turn product back log into increment of functionality
  through iterations
• Typically 5 - 9 people
• Members should be full-time

Question 26

Scrum meetings

Answer 26

Sprint Planning Meeting
Daily Scrum Meeting
Product Backlog Refinement Meeting
Sprint Review Meeting
Sprint Retrospective Meeting

Question 27

Sprint planning meeting

Answer 27

– Product Owner provides the prioritized Product Backlog
– Dev Team creates a plan to achieve the goal (Sprint
Backlog.
– Scrum Master facilitates the meeting, and coaches as
needed
Normally Meeting is time boxed to 2 hours

Question 28

Daily stand-up meeting

Answer 28

Objective : discuss activities and create a plan for the next 24
hours
Duration – 15 minutes ever day within the sprint

Question 29

Sprint Review Meeting

Answer 29

• Hold at the end of the sprint.
  Purpose: Inspect and Adapt the Product
• Normally Time boxed to 1 hour
• Product Owner, Dev Team, Scrum Master, and
  stakeholders get “hands on” with the product

Question 30

Sprint Retrospective Meeting

Answer 30

• Hold after the sprint review meeting
• Purpose: Inspect and Adapt Our Process
• Scrum Team to inspect itself and create a plan for
  improvements to be enacted during the next Sprint.

Team members should answer two questions
– What went well during the sprint? (people, relationships,
process, and tools)
– What could be improved in the next sprint?

Question 31

Sprint Retrospective Meeting