Loading presentation...

Present Remotely

Send the link below via email or IM


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.


Agile Development

No description

Mia Cadieux

on 16 September 2015

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Agile Development

Scrum Master
Beginning Scrum
What type of projects best suit Agile?

Quick, simple frame work
Uses efficient and effective teams
Used for software projects and more
Flexible and adaptable
What is Scrum?
Agile Development
By Alex, Mia, Patrick, and Nick
Before the concept of agile development, methods such as waterfall, incremental, and spiral were used
A Brief History on Agile Development
Sprints (Short duration Milestone)
Finished Poduct In a Ship ready state
Estimates from release backlog broken down into "sprints"
Can be a couple to 30 days in length
Must be done on deadline or there is an issue
Standup meetings allow for quick adaptation
Well executed agile project
Excellent team coordination
Scrum masters are also experienced agile coaches
Removed slow working teams
Innovative project (wanted to compete with big players: Amazon, Google, etc...)

Examples of Agile Projects
Agile Model - Advantages
Agile Model - Disadvantages

Fernandez, E. (2014, January 16). Two Examples of Agile Done Right and Agile Gone Wrong | OpenView Labs. Retrieved September 14, 2015.

Gauged in the complexity of the user stories
Helps breakdown each part of the software project
Helps team prioritize and organize for maximum efficiency
The Agile Manifesto States:

Individuals and interactions
over processes and tools
Working software
over comprehensive documentation
Customer collaboration
over contract negotiation
Responding to change
over following a plan

That is, while there is value in the items on the right, we value the items on the left more.”
The Agile Manifesto

Projects with:
High Degree of Complexity
Aggressive Timelines
Highly Innovative
Poorly executed agile project
Lack of coordination between teams, Scrum master, and Product Owner
Weak leadership and guidance
Had lots of failed sprints

Product Owner
The burndown velocity shows the average rate of productivity each day.
The Burndown Chart
Leaders began promoting organizations to quickly react and adapt to changing requirements and technologies
These innovative approaches, along with embracing change, would result in success
By the late 1990s, the software development processes that had been developed in the 80s and 90s were being criticized as bureaucratic and slow
Tracks daily remaining amount of work
Allows for daily feedback
Allows for effective insight into how the project is going
Gives recorded information about sprints for retrospective
Each aspect of development being constantly revised
Keeps up with the new ideas on the market
Saves time and money that would be spent on updates for present
Allows for constant revision and improvement
The customers' needs are more heavily valued and software is less generalized

Shorter, lightweight processes which save time and money

Flexible contracts which give companies the competitive advantage
Agile Today
Aggressive Timeline
Highly Innovative
High Degree of Complexity
Unsure of how to reach final product
ex. Ford knows how to build a car but Google may not know how to create next generation self driving vehicles
Complex projects often lead to changes of requirements which is well supported by Agile
ex. Internal system for managing inventory in a multinational web store (Amazon)
Sprints allow for team to discover technical issues early and revector the project to address these issues
Allows for changes to be made to requirements to meet aggressive timelines
ex. Key features can be implemented to satisfy stakeholders in version 1, other features can deferred to later versions
Innovation means uncharted territory, technical uncertainty, and high risk
The project has to be able to undergo a large series of alterations
“Agile allows for the freedom to make changes as necessary, without the shackles of an outdat
document” Idealist Consulting
Agile is now used as an umbrella reference to numerous lightweight development methods
rapid, continuous Working software

Promotes Interaction

More flexible changes

very limited planning
easily get taken off track

senior programmers are required

Difficult to Assess the Effort Required at the Beginning

Frantic and stressful
Agile vs Waterfall Success Rate
It has become one of the most popular software development methods, and is considered to be the best by some experts
Extreme programming focuses on software engineering and the development phases of the project
DSDM is the original agile method and has been around since before the term 'agile' was used
Kanban is based on visualizing, limiting work in progress, and enhancing work flow
Full transcript