BEFORE AGILE METHODS Other Engineering fields development models were used, ie: Waterfall Method: Intensive planning and refactoring before coding is actually done Pros: Great documentation and works well with other engineering fields Cons: Increases man hour costs which are the most expensive part of software development
Other Engineering fields development models were used, ie: Waterfall Method: Intensive planning and refactoring before coding is actually done Pros: Great documentation and works well with other engineering fields - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
BEFORE AGILE METHODS
Other Engineering fields development models were used, ie:
Waterfall Method: Intensive planning and refactoring before coding is actually done
Pros: Great documentation and works well with other engineering fields
Cons: Increases man hour costs which are the most expensive part of software development
BETTER METHODOLOGY NEEDED
1. Lots of dead time when creating specifications.
2. Not reuse oriented. 3. Software may be obsolete or have no market
by the time its released. 4. 80% of software projects failed
LOOK TO TOYOTA
Toyota Production System 3 Principles:
1. Build only what is needed. 2. Eliminate anything that doesn't add value. 3. Stop if something goes wrong.
LEAN THINKING
5 principles derived from Toyota's model, book published 1996:
1. Specify value. 2. Identify the value stream. 3. Create the conditions for value to flow
smoothly through the stream. 4. Have the customer pull value from the
stream. 5. Pursue perfection.
SCRUM
1. First agile method where work is done iteratively in sprints.
2. Sprints are typically 2 to 4 weeks. 3. Customer can change requirements during
project.
AGILE MANIFESTO 2001 We are uncovering better ways of developing
software by doing it and helping others do it. Through this work we have come to value:
1. Individuals and 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. 5. That is, while there is value in the items on the
right, we value the items on the left more.
Fundamentals of Extreme Programming
1. Pair programming 2. Planning game 3. Small releases 4. Continuous testing 5. System metaphor 6. Simple design
development techniques that are more loose and less corporate are more likely to spread.
Innovation in assemblyReusable and highly accessible tools will challenge the proprietary standards.
Cross-functional teamsNo more compartmentalizing your developers. Teams and projects, like ideas, should flow freely.
Agile in the Industry PROS & CONS What are some of the disadvantages of Agile? 1. Active user involvement and close
collaboration are required throughout the development cycle.
2. Requirements are revealed and evolve over time.
3. Agile requirements are intentionally minimal. 4. Testing is integrated throughout the lifecycle. 5. Feature sign off’s are required. 6. Agile development can be intense for
developers.
IS AGILE FOR US?
Vital questions:
1. Do companies have to just choose either Waterfall or Agile or are there hybrid options?
2. What questions should be asked? How can a company decide whether to implement Agile methodologies?
Is the project suitable for Agile?
1. Does the project have a lot of ambiguity and uncertainty?
2. Does the product already exist or is this project starting from scratch?
3. How critical are the operations of the final product?
Is the team suitable for Agile?
1. Does the Product Owner have the right level of authority and influence?
2. Is there a dedicated, persistent, cross-functional team?
3. Is the team co-located? 4. Do you have an Uber Product Owner and
Uber ScrumMaster? 5. Is there a controlled build environment?