42
IE/ME 4255 Multidisciplina ry Senior Design Ryan G. Rosandich, Ph.D. Associate Professor, MIE Agile Project Management

Ryan G. Rosandich, Ph.D. Associate Professor, MIE Agile Project Management

  • View
    219

  • Download
    2

Embed Size (px)

Citation preview

  • Slide 1
  • Ryan G. Rosandich, Ph.D. Associate Professor, MIE Agile Project Management
  • Slide 2
  • Agile Characteristics High speed Changing requirements Quality results
  • Slide 3
  • The Agile Manifesto Responding to change over following a plan Working products over comprehensive documentation Customer collaboration over contract negotiation Individuals and interactions over processes and tools
  • Slide 4
  • Responding to change Envision and explore, not plan and do Adapting instead of anticipating Goal oriented, not task oriented Short term plan, long term change
  • Slide 5
  • Working products Short term deliverables that are real Drawings, specifications, bid packages Products, models, or prototypes Has value to customer Less emphasis on documentation Fewer reports Documents developed interactively, not exchanged Quick meaningful feedback from customers
  • Slide 6
  • Customer Value What they are willing to pay Meeting expectations Product performance (now and later) Cost/budget Schedule/delivery Expectations and requirements Requirements are fixed and stated up front Expectations evolve with the project
  • Slide 7
  • Project Participants Deliver Value Everyone has the vision Goals known Customer known Motivated, self-directed participants Decision making at the lowest level
  • Slide 8
  • Customer collaboration Customer or proxy? Customer or stakeholder? Customers define value Stakeholders define constraints Higher uncertainty means higher customer collaboration
  • Slide 9
  • Individuals and interactions Individuals produce goods and services Unique talents and experience Unique personalities and behavior Creators and stewards Good processes Support people Adapt to the needs of people Good tools improve efficiency People make decisions
  • Slide 10
  • Agile Project Managers Leaders, not enforcers Managers, not administrators Enable rather than hinder progress Add value to the project rather than creating busy work Would the customer pay for this?
  • Slide 11
  • How much structure do we need? Too much Stifles creativity Rigidity Predictable results Not enough Inefficiency Chaos Balance of flexibility and stability
  • Slide 12
  • Agile Project Management Framework Envision Speculate Explore Adapt Close Iterative
  • Slide 13
  • Iterative Development Short iterations Real deliverables Incremental improvements Lower cost commitment per iteration Product representations Models Simulations Prototypes
  • Slide 14
  • Envision Phase What is the vision for the product? What are the objectives and constraints? Who will be involved in the project? How will they deliver the product (vision)?
  • Slide 15
  • The Vision Thing A good vision Is clear (but details are fuzzy) Is an obvious improvement or advancement Creates a sense of urgency and/or excitement Apollo moon project
  • Slide 16
  • Elevator Test Statement For (target customer) who (want or need) The (product) is a (product category) that (reason to buy) Unlike (competition) our product (primary differentiation)
  • Slide 17
  • Product Vision Name Graphical representation Key selling features (3-4) Detailed feature description Operating requirements Package, brochure, web page
  • Slide 18
  • Product Architecture Feature breakdown structure Platform Components Modules Interfaces Project team structure and organization Guiding product principles (