1 / 18

Iterative Project Management

Iterative Project Management. Lifecycle Planning Chapter 6 – Overall Project Planning Modified Considerably by your Instructor. Problem Statement

nessa
Download Presentation

Iterative Project Management

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Iterative Project Management Lifecycle Planning Chapter 6 – Overall Project Planning Modified Considerably by your Instructor

  2. Problem Statement Theproblem of having convenient and secure access to banking balances to withdraw funds, manage accounts or purchase automatically dispensed goods Affectscustomers of financial organizations and vendors using transactional paper based currency (tickets, paper-based goods etc) Impact: low customer satisfaction and high transaction costs Successfulsolution: allowa customers access to their assets and the ability to transform them into other forms of paper based currency Product Position Statement For financial institutions and vendors of paper based goods Who own or manage automated teller networks The ACME Super ATM is an automated teller machine That provides lowered cost of ownership and flexible definition of new transaction types and dispensable paper goods Unlike conventional ATM devices and ticket machines Our product utilizes standard computing platforms and component technology to provide a flexible, generic, extensible but low-cost platform for managing customer transactions and dispensing goods Intro To Example: Excerpts from the Vision of The ACME Super ATM Iterative Project Management / 03 - Lifecycle Planning

  3. Principle 1: Understand the Desired Outcomes Balanced scorecard: provides a good way to summarize desired outcomes for project. Forces project to consider a number of perspectives some of which are often forgotten in planning IT projects. Objectives should be complemented with measures and targets. Must understand what the project needs to achieve to be successful. Iterative Project Management / 03 - Lifecycle Planning

  4. Business Risks Market may be too crowded with competitors May not be able to price product aggressively enough to displace competitors Cost to develop may be too high Profit margin may provide insufficient return on investment Customers may not want a new or more flexible solution No future market for paper based goods (tickets etc) Technical Risks PC/Windows-based platform may not be reliable enough for remote/unattended use System may not “fail gracefully” if power or network connection is lost in the middle of a transaction System may not be able to be made “tamper-proof” especially the device ‘charging’ May not be able to deliver a sufficiently flexible, component-based system at low cost Underlying technology (J2EE) may not perform sufficiently well to meet needs Printing may not be flexible or reliable enough Principle 2: Identify and assess overall risks (This list is incomplete…) In the UP, risk becomes the dominant factor in planning iterations! Iterative Project Management / 03 - Lifecycle Planning

  5. Principle 3: Set the Management Strategy (bolds are mine) • Style of Delivery • Staged iterative and incremental delivery • Co-located teams • Level of ceremony and formality • The project will be low ceremony with high levels of user / stakeholder involvement • Adopt standard QA process with central governance • Process selection • Unified Process, small project tailoring • Risk management using Top 10 risks (RM Plan) • Reporting and communications • Primary reporting mechanism – iteration assessment • User Acceptance • Independent user acceptance and system test • Stakeholders involved in all iteration and phase reviews Iterative Project Management / 03 - Lifecycle Planning

  6. Principle 4: Create an Achievement-Based Roadmap Basis for overall project planning including compelling events, business milestones, stepping stones, and the approach / strategy to deployment Technology Piloted Existing ATMs Replaced ATMs Upgraded ConfigurableDispensingProved Basic WithdrawalImplemented CurrentAccountManagement Full AccountManagement Super ATM for Banking Launched Cross Selling &Advertising SystemsManagement Vending PlatformSpecification Agreed TicketDispensingIntroduced Basic PrintedGoods Production Full PrintedGoods Production Demonstration atInternational RailConference Ticket PartnerRecruited Iterative Project Management / 03 - Lifecycle Planning

  7. Principle 5: Understand the solution and its scope Refill and Service the Machine Purchase Goods Purchase Tickets Configure the Machine Withdraw Cash ATM Engineer Check the Machine is in Working Order Deposit Funds Customer Analyze System Performance Transfer Funds Reconcile Transaction Logs Manage Account Charge Device WithFunds ATM Operator Run Advertising Campaign Update System Configuration Break Into Machine Burglar Change Pricing System-level Use Case Diagram showing all Actors Iterative Project Management / 03 - Lifecycle Planning

  8. Principle 6: Assess and Estimate the Work to Be Done • For each use case • Prioritize from a customer perspective • Assess the architectural significance • Create an estimate • For each component • Assess size and complexity • Create an estimate • Compare to earlier developments • Create an estimate There are many techniques for the estimation of software projects planning. These include use-case points, function points, analogy, COCOMO II, etc. Perform triangulation on the estimates to produce a consensus view of the overall cost and effort. Iterative Project Management / 03 - Lifecycle Planning

  9. Principle 7: Define the External Release Plans ConfigurableDispensingProved CurrentAccountManagement Full AccountManagement Basic WithdrawalImplemented SystemsManagement Cross Selling &Advertising Full PrintedGoods Production Printed Goods Capability Proved Basic PrintedGoods Production Release 4 & Up Release 1 Release 2 Release 3 Structure the roadmap to reflect the external releases. Must have total stakeholder buy in to these planned releases. Iterative Project Management / 03 - Lifecycle Planning

  10. External Release Planning - Adding in the Process Milestones Shows evolution / external release and stage planning using the Unified Process cycles. We do not consider planning anything other than our agreed commitments and major business milestones at this time Stage 4 Stage 1 Initiation Stage 2 Stage 3 Release 1: Basic Withdrawal Facilities Trans Inception Elab Con Release 2: Account and Systems Management Inc Con Trans Elab Release 3: Full Account Management and Printed Goods Trans Elab Con Inc Release 4: Full PrintedGoods Production Trans Elab Con Inc Iterative Project Management / 03 - Lifecycle Planning

  11. External Release Planning: Select From The Use Cases Note that use-case scenarios are designed and implemented during planned releases. Refill and Service the Machine Purchase Goods Purchase Tickets Configure the Machine Withdraw Cash ATM Engineer Check the Machine is in Working Order Deposit Funds Customer Analyze System Performance Transfer Funds Reconcile Transaction Logs Manage Account Charge Device WithFunds ATM Operator Run Advertising Campaign Update System Configuration Break Into Machine Burglar Change Pricing Release 1: , Release 2: , Release 3: , Release 4: , Out of Scope: Iterative Project Management / 03 - Lifecycle Planning

  12. Principle 8: Delegate the Execution of the Plans • To get anything done, a team must be put together and an iteration executed • Based on the framework provided by the initial risk list, roadmap, vision, business case and a lifecycle plan for the evolution / external release • Start to sketch out the iterations • Decide who will manage the evolution / external release • Allocate and recruit resources • Start iterating As soon as you can, take the highest risks, and highest priority objectives, and start to address them by producing a release of the software Iterative Project Management / 03 - Lifecycle Planning

  13. Inception Phase Risks Mitigated: Crowded market Product pricing and profitability Customer demand for configurable transactions Scenarios: Withdraw Cash Configure Transaction Elaboration Phase Risks Mitigated: Reliability of OS platform Scalability of J2EE infrastructure Fault tolerance Tamper-proofing Printing flexibility & reliability Elaboration Phase (continued) Scenarios: Break into Machine Withdraw Cash + Bank System Stopping Responding Withdraw Cash Basic Flow + Handle Transaction Log Failures Withdraw Cash (scenarios in parallel) Simple ticket printing Construction Phase Risks Mitigated: Completing work on time, within budget All remaining scenarios Partial Plan for the ACME Super ATM Release 1 Notice the beauty of this approach: Capture the risks/ address the mitigation of the risks and design the solution to mitigate the risks as captured in use-case scenarios. Iterative Project Management / 03 - Lifecycle Planning

  14. Summary of Increments for ACME Super ATM Release 1 This release is heavy on architecture. Heavy risk is addressed via the architecture and its realization Iterative Project Management / 03 - Lifecycle Planning

  15. Principle 9: Iteratively Evolve and Challenge the Plans • We must act upon the empirical evidence provided by the iterations • The end of phase reviews must be taken seriously as decision points • The phase success criteria must be met before proceeding to the next phase • We must be prepared to rework and continuously adjust the plans • Iterations provided empirical evidence • Lagging indicators • Current indicators • Leading indicators If the plans don’t change – be afraid, be very afraid. Iterative Project Management / 03 - Lifecycle Planning

  16. Summary and Review: Planning, planning, planning! • Multiple levels of plan are required: • Overall project plan – benefits focused • Development plan – evolution / external release focused • Iteration plan – task / activity focused • The plans are related by milestones and achievements • The UP milestones provide a roadmap for the development of the system • The detail resides in the iteration plan • The higher level plans exist to record commitments and allow impact analysis • Don’t do detailed planning for more than one iteration ahead Iterative Project Management / 03 - Lifecycle Planning

  17. Planning and Management Products According to Kurt Bittner, we are focused here on planning and assessment of the project. Elements of the management strategy need to be discussed where they are impacted by the introduction of iterative development practices. Iterative Project Management / 03 - Lifecycle Planning 17

  18. Management Responsibilities and Reviews These three management roles share the responsibilities of the traditional UP Project Manager role. For the project to be ‘joined up’ the managementmust work as a team to plan and assess the project. Iterative Project Management / 03 - Lifecycle Planning 18

More Related