1 / 18

Mark Parker (800) 984-9346 mark.parker@outliertech

National Association for Regulatory Administration September 13, 2011 IT’s NOT Like Building a House. Mark Parker (800) 984-9346 mark.parker@outliertech.com. Overview. Sequential

hope
Download Presentation

Mark Parker (800) 984-9346 mark.parker@outliertech

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. National Association for Regulatory AdministrationSeptember 13, 2011IT’s NOT Like Building a House Mark Parker (800) 984-9346 mark.parker@outliertech.com

  2. Overview • Sequential (Waterfall, BDUF – Big Design Up Front) development that proceeds from one phase to the next in purely a sequential manner; each phase must be completed and perfected before moving to the next phase. In a sequential model, there is no going back to a previous phase and no overlapping of phases. • Iterative and Incremental (XP – Extreme Programming, RAD – Rapid Application Development, UP – Unified Process, RUP – Rational Unified Process, Spiral, Scrum) development that proceeds in repeatable iterations to iteratively and incrementally enhance and evolve a program until it is accepted by the user. The goal for design and development of any iteration is to be simple, straightforward and modular, supporting redesign at any time or as tasks are added. In an iterative and incremental model, iterations may be repeated and phases may overlap. There are many different methodologies for software development, each describing approaches to a variety of tasks or activities that take place throughout the software development lifecycle. Generally speaking, all software development methodologies fall into one of two categories.

  3. Sequential Software Development Waterfall, BDUF – Big Design Up Front Requirements Design Code Test Deploy

  4. Iterative and Incremental Software Development XP – Extreme Programming, RAD – Rapid Application Development, UP – Unified Process, RUP – Rational Unified Process, Spiral, Scrum

  5. Scientific Method

  6. Scientific Method and Iterative Development http://en.wikipedia.org/wiki/Iterative_and_incremental_development http://www.makeitsolar.com/science-fair-information/01-the-scientific-method.htm • Choose Your Topic • Identify Problem • Research Problem • Develop Hypothesis • Design Experiments • Test the Hypothesis • Analyze Results • Formulate Conclusions • Initial Planning • Planning • Requirements • Analysis • Design • Implementation • Testing • Evaluation

  7. Outcomes Experiment Iteration • Increased Knowledge • Decision Point • Problem Solved • Increased Knowledge • Decision Point • Deployment

  8. Unified Process - UP • Risk Focused • Results Oriented • Architecture Based • Use Case Driven • Developer Centric • Stakeholder Collaborative

  9. Why Iterative? “The fundamental reason that a project iterates is to reduce risk.” 100% Project Risk Exposure Project Schedule Target Completion Date Sequential (Waterfall) Iterative and Incremental

  10. Unified Process Hierarchy Evolution Phases Inception Elaboration Construction Transition Iterations

  11. Evolution • Defines the deliverable • A small part or component of a larger information system • Is a 3 to 6 month development effort

  12. Inception Phase • Risk Focus • Business • Questions • Are we building the right thing? • Is the solution feasible? • How Much? • Outcome • Agreement to fund

  13. Elaboration Phase • Risk Focus • Architectural • Questions • What are the unknowns? • What are the technical risks? • How will the technical risks be mitigated? • Outcome • A stable, proven, executable architecture

  14. Construction Phase • Risk Focus • Logistical • Questions • Do our assumptions and earlier decisions hold? • Will it be done on time? • Are the users ready? • Outcome • A useful, tested, deployable and documented solution

  15. Transition Phase • Risk Focus • Roll-out • Questions • Is it acceptable? • Is it being used? • Can the customer maintain and further enhance the solution? • Outcome • The solution is in “actual use”

  16. Unified Process Summary • Reduces Risk (All Stakeholders) • Large projects are broken down into “Mini Projects” • Multiple review and decision points throughout the process • Based on the Scientific Method • Focuses on Delivering Business Value

  17. The Book Managing Iterative Software Development Projects By Kurt Bittner Ian Spence

  18. Thank you Mark Parker (800) 984-9346 mark.parker@outliertech.com

More Related