Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Agile Development

No description
by

Zoe Azhdari

on 23 July 2015

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Agile Development

Not a process, it's a philosophy or set of values
Agile Development
in a nutshell
Principles of Agile

Requirments
Design
Development
Testing
Maintenance
Traditional approach
Design
Maintenance
Design
Requirments
Development
Testing
Agile Manifesto
Things we do:
1. The project/product is described as a list of features:
The Backlog

2. The time box you spend to develop selected features is called
sprint.

3. The features are described in terms of
User Stories.

3. The team
estimates
the work associated with each story

5. Features in the backlog are
ranked
in order of importance

Result: a prioritized and weighted list of product features, a
road map
How it happens
Tools
JIRA
Agile Board
THANK YOU
Requirments
Design
Development
Testing
Maintenance
Changes
Takes too long
Skipped or delayed
Side effects
You don't realize any value till the end of the project
You leave the testing until the end
You don't seek approval from the stakeholders until late in the day

Agile Manifesto
Individuals and interactions over processes and tools
Agile Manifesto
Working software over comprehensive documentation
Agile Manifesto
Responding to change over following a plan
Agile Manifesto
Customer collaboration over contract negotiation
1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter time-scale.
3. Working software is the primary measure of progress.
4. Welcome changing requirements, even late in development
5. Simplicity, the art of maximizing the amount of work
not
done, is essential.
6. Continuous attention to technical excellence and good design enhances agility
7. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly
8. Business people and developers must work together daily throughout the project.
9. The most efficient and effective method of conveying information to and within a development team is face-t-face conversation.

10. The best architectures, requirements, and designs emerge from self-organizing teams.

11. Build projects around motivated individuals. Give them the environment and support their needs, and trust them to get the job done.

12. Agile processes promote sustainable development. The sponsors, developers and users should be able to maintain a constant pace indefinitely.

Daily Stand ups
Backlog Grooming
Show and Tell
Retrospective
Sprint Planning
Sprint Planning
Daily Stand ups
What did you do yesterday?
What will you do today?
Any blocker?
Backlog grooming
re-prioritization
Change of requirements
New Bugs/ features

Show and tell
Retrospective
What did we do
Good
last sprint?
What was
Bad
?
What we would do
Never again?
Before sprint starts
Estimate stories
Testing and regression test
Bugs
!=
stories


Demo of sprint's work
Invite as many people as possible


Zoe Azhdari
Full transcript