SE-3 Flashcards
Agile development
➢ Set of methods & methodologies
➢ Made up of a number of good practices
➢ Help a team think & work more
efficiently.
Benefits of agile
Deliver on time & budget
Deliver a high-quality product
Deliver a maintainable code
Make the client happy
Work happy
Agile Manifesto
- Individuals & interactions over process & tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
Agile principles
early release of the developing
product to the customer.
▪ Getting rapid feedback from the
customer & incorporating that feedback
into new design experiments.
Agile software development life cycle
- Plan
2.Design
3.Develop
4.Test
5.Deploy
6.Review
7.Launch
1.Agile:Requirement Gathering
Define the requirements.
▪ The features your application will provide
▪ Should explain business opportunities
Features of good requirements
➢ Clear
➢ Unambiguous/obvious
➢ Consistent
➢ Prioritised
Agile:. Design the requirements
to show the work of new features and show how it will
apply to your existing system.
Agile: Develop/ iteration:
start working on their project,
which aims to deploy a working product.
Agile: Testing
Quality Assurance team examines the product’s
performance and looks for the bug
Agile: Deployment
issues a product for the user’s work
environment.
Agile: Feedback/Review
team receives feedback about the product and
works through the feedback.
Agile methodologies
scrum
Scrum Process
an agile project management framework
that helps teams structure and manage their work
through a set of values, principles, and practices.
Sprint
break work into
goals to be completed within time-boxed
iterations, called sprints.
Sprint
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.
Kanban board
Arrangement of columns to track work progress
Each column represents a step in the development process
Easy to identify progress and bottlenecks
Burn Down Chart
Updated before every Daily Standup Meeting
Scrum Master adds up the estimated hours for all
remaining tasks on the Kanban board
Scrum Artifacts
- Product backlog
- Sprint backlog
- Increment
Product backlog
Includes Requirements for the system or product being
developed
* Product owner is responsible for the contents,
prioritization and availability of product backlog
Sprint backlog
Set of Product Backlog items selected for the Sprint
Plan for delivering the product Increment and realizing
the Sprint Goal.
Increment
Scrum requires team to build increment/slice of the
product of functionality
* Definition of ‘Done’
The scrum team
–Product Owner
–Scrum Master
– Development Team
Scrum Master
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
Product owner
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