introduction to agile methodologies and concepts n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Introduction to Agile Methodologies and Concepts PowerPoint Presentation
Download Presentation
Introduction to Agile Methodologies and Concepts

Loading in 2 Seconds...

play fullscreen
1 / 18

Introduction to Agile Methodologies and Concepts - PowerPoint PPT Presentation


  • 114 Views
  • Uploaded on

Introduction to Agile Methodologies and Concepts. Roy Osherove Principal, Team Agile www.TeamAgile.com Blog : ISerializable.com. Methodology. Code – and – fix (long test/debug phase) Methodology (more predictable, efficient) Detailed process, big on planning Engineering methodologies

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Introduction to Agile Methodologies and Concepts' - vaughan-cantrell


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
introduction to agile methodologies and concepts

Introduction to Agile Methodologies and Concepts

Roy Osherove

Principal, Team Agile

www.TeamAgile.com

Blog: ISerializable.com

methodology
Methodology
  • Code – and – fix (long test/debug phase)
  • Methodology (more predictable, efficient)
    • Detailed process, big on planning
  • Engineering methodologies
    • Successful? popular? criticized?
  • Lightweight methodologies (agile)

Process

Cowboy

Agile

agile properties
Engineering

Predictive

Process-Oriented

Agile

Adaptive

People-Oriented

Agile properties
predictive vs adaptive
Predictive vs. adaptive
  • Separation of Design and Construction
  • Comparative cost
  • The Unpredictability of Requirements
  • Is Predictability Impossible?
  • Pretending
  • Controlling an unpredictable Process
predictive vs adaptive 2
Predictive vs. adaptive (2)
  • The Adaptive Customer
  • Different relationship
  • Fixed price?
    • Needs stable requirements (predictive)
    • Customer loses more even if 0$ paid
    • Success = On time & on cost
  • Can fix time & budget, but not scope
    • Finer grained control by the customer
    • Responsive development
    • Visibility (manage risks early)
    • Success = Customer value > cost
putting people first
Putting People First
  • Plug Compatible Programming Units
    • Predictable process requires predictable parts
    • Good with machines ~= bad with people
    • Careful what you wish for
  • Programmers are Responsible Professionals
  • Managing a People Oriented Process
      • Accepting the process
      • Equal part for management and team
putting people first 2
Putting people first (2)
  • The Difficulty of Measurement
    • Measurement based management is good for simple things
    • We can’t measure software
    • Delegatory management
  • The Role of Business Leadership
    • Teams need contact with business expertise (customer)
    • Not occasional communication, but constant
  • The self adaptive process
the methodologies
The Methodologies
  • XP
  • The Crystal family
  • MSF- Agile
  • Highsmith's ASD (Adaptive Software Development)
  • Scrum
  • Feature Driven Development
  • DSDM (Dynamic Systems Development Method)
  • Rational Unified Process? (dX)
the agile manifesto
The Agile Manifesto

“We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

  • 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. “

stepping towards agile development
Stepping towards Agile Development
  • Daily Stand Up Meetings
  • Daily Build (CI)
  • Unit Testing (+ TDD?)
  • Customer Testing
  • Mixed Teams
  • Smaller Iterations
what is xp

What is XP?

A brief introduction

Communication, Simplicity

Feedback, Courage

when to use xp
When to use XP
  • dynamically changing requirements
  • Risky projects
  • Small dev groups (up to 100)
  • Non-fixed scope(price) contract
simple rules and practices
Planning

Release Planning

Iterations Planning

User Stories

Small Releases

Measure Project Velocity

Move People around

Stand up meeting

Designing

Simplicity

System Metaphor

CRC cards

Spike solutions

YAGNI

Refactor

Simple rules and practices
simple rules and practices1
Coding

Customer available

Code standards

Test-Driven

Pair Programming

Sequential change integration

Integrate often

Collective code ownership

Don’t optimize early

No overtime

Testing

Unit test everything

All tests pass before release

Bug== new test

Acceptance tests

Simple rules and practices
thank you

Thank You!

Roy@TeamAgile.com

www.TeamAgile.com