z26 project management agile and iterative planning lecture 2a graham collins ucl
Skip this Video
Download Presentation
Z26 Project Management Agile and Iterative Planning Lecture 2a Graham Collins, UCL

Loading in 2 Seconds...

play fullscreen
1 / 26

Z26 Project Management Agile and Iterative Planning Lecture 2a Graham Collins, UCL - PowerPoint PPT Presentation

  • Uploaded on

Z26 Project Management Agile and Iterative Planning Lecture 2a Graham Collins, UCL. [email protected] Phases of UP. Inception. Agreement on scope Elaboration. Vision, requirements and architecture stabilized, build and test risky core several iterations

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

PowerPoint Slideshow about 'Z26 Project Management Agile and Iterative Planning Lecture 2a Graham Collins, UCL' - ivan-dudley

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
phases of up
Phases of UP
  • Inception. Agreement on scope
  • Elaboration. Vision, requirements and architecture stabilized, build and test risky core several iterations
  • Construction. Build and test the rest, largest set of iterations
  • Transition. System deployed, beta testing, release evaluation, training
useful websites
Useful websites
  • www.agilealliance.com
  • www.agilemodelling.com
  • www.martinfowler.com
  • www.jimhighsmith.com
  • www.alister.cockburn.com
  • www.controlchaos.com
  • www.dsdm.org
  • www.rational.com
further reading
Further reading

Kent Beck (2000), Extreme Programming explained:embrace change, Addison-Wesley ISBN 0-201-61641-6

Jim Highsmith (2002) Agile Software development Ecosystems, Addison-Wesley ISBN 0-201-76043-6

Paul Allen (2002), Realizing e-Business with Components, Addison-Wesley ISBN0-201-67520-X

Walker Royce (1998), Software Project Management: A Unified Framework, Addison-Wesley ISBN 0-201-30958-0

Ian Graham et al (1997) ,The OPEN Process Specification, Addison-Wesley ISBN0-201-33133-0

Murray Cantor (2002) Software Leadership: A Guide to Successful Software Development,Addison-Wesley, ISBN 0-201-70044-1

Philippe Kruchten (2000) The Rational Unified Process an Introduction, Second Edition, Addison-Wesley new edition being published

Ian Graham (1998), Requirements Engineering and Rapid Development: An object-Oriented Approach, Addison-Wesley ISBN 0-201-36047-0

predictable projects
Predictable projects
  • Possible to complete specifications then build
  • Near start can estimate effort and cost
  • Possible to define schedule and order activities
  • Adaptation to unpredictable change not ‘normal’
innovative projects
Innovative projects
  • Cannot create upfront unchanging annd detailed specification
  • Only as empirical data emerges is it possible to plan and estimate
  • Adaptive steps driven by build-feedback cycles are required
  • Creative adaptation the norm.
plan driven approaches
Plan Driven Approaches
  • Plan driven methods are considered the traditional way to develop software
  • Methods encourage a waterfall style approach
  • Requirements/design/build/test paradigm
  • Well defined processes that organisations continuously improve
introduction of standards
Introduction of Standards
  • MIL-STD-1521
  • IBM
  • Siemens
  • Often for internal use
software engineering
Software Engineering
  • Process discipline and structured techniques were developed
  • Fitted well with the concept of formal mathematical specification and verification
  • Well defined work products
  • Verification and validation
  • Although iterative and incremental processes (evolutionary) processes have gained momentum, still a high documentation and traceability mandates across requirements, design and code
process improvement cycle
Process Improvement Cycle

Improve Process

Define Process

Control Process

Measure Process

Perform Process

plan driven concepts
Plan-driven Concepts
  • Process improvement
  • Process capability
  • Organizational Maturity
  • Process group
  • Risk management
  • Verification and validation
  • Software systems architecture
document generation rather than software development
Document generation rather than software development

‘Planning can cause problems. If too strictly applied, plans and processes can impede innovation or lead to mechanical check list mentality, where the object of the endeavor becomes so focused on the process that the product (often along with the customer) is afforded secondary status.

Barry Boehm & Richard Turner (2004), Balancing Agility and Discipline: A guide for the perplexed, Addison-Wesley

ISBN 0-321-18612-5

extreme programming xp
eXtreme programming (XP)
  • Planning game
  • Small frequent releases
  • System metaphors
  • Simple design
  • Testing
  • Frequent refactoring
  • Pair programming
  • Team code ownership
  • Continuous integration
  • Sustainable pace
  • Whole team together
  • Coding standards
  • Self directed and self-organizing teams
  • No external addition of workload to an iteration
  • Daily stand-up meetings
  • 30 day iterations
  • Client driven iterations with demo at end of each to client
unified process
Unified Process
  • Development in short timeboxed iterations
  • Develop high-risk high value first
  • Use case driven
  • Architecture centric
  • Accommodate changes early
  • Work together as a team
adaptive planning
Adaptive Planning






Milestone 1 1st May R1…R10 complete

Milestone 2 1st July R11…R20 complete

improving estimates with wideband delphi
Improving estimates with Wideband Delphi
  • Kickoff meeting
  • Estimation
  • Meeting
  • Repeat steps
  • Calculate
  • Team members estimate their time budget each iteration
  • Volunteering
  • Visible project plans
  • Iteration Goals: risks, coverage, criticality, (examples demo of product, skills development)
tracking iteration progress
Tracking Iteration Progress
  • Frequent
  • Wall list for small projects
  • XP task cards held by the volunteer
  • Asking team members to self-record their remaining task effort. Better XP practice of a ‘daily tracker’.
  • Test driven development
earned value
Earned value
  • Recognition rules
  • ‘rubber baseline’
  • Experimental stage
  • Philippe Kruchten article
risk management
Risk Management

Then develop a management plan on wall, ie risk, actions, owner, status

  • Continuous integration
  • Project Wiki webs
  • Reverse engineering- Somatik

Caves, walls, digital technology