Dilbert Scott Adams.

Slides:



Advertisements
Similar presentations
1 Requirements and the Software Lifecycle The traditional software process models Waterfall model Spiral model The iterative approach Chapter 3.
Advertisements

Software Life Cycle Requirements analysis System design Program design Program implementation (coding) Unit testing Integration testing System testing.
AgileMan Consulting So what the heck is Agile? It came about as a response to the high failure rate of software projects (> 60%), where failure means late,
Modeling the Process and Life Cycle CSCI 411 Advanced Database and Project Management Monday, February 2, 2015.
Sharif University of Technology Session # 3.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
A Prototyping Lifecycle. The Waterefall Model and Prototyping 4 As early as the 1980’s the classic “Waterfall model” of software development was criticised.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Software Development Overview CPSC 315 – Programming Studio Spring 2009.
Software Development Overview CPSC 315 – Programming Studio Spring 2008.
Agile software development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions.
Chapter 1 The Systems Development Environment
Capability Maturity Models Software Engineering Institute (supported by DoD) The problems of software development are mainly caused by poor process management.
Chapter 2 Software processes. Topics covered Software process models Process activities Coping with change.
The Spiral Model Sultana & Mahmood. Systems development life-cycle The process of creating or altering computer systems The models that define the processes.
Software Development Overview CPSC 315 – Programming Studio Spring 2013.
© 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v
Agile. Processes Waterfall Traditional With prototyping Sprial Agile Dynamic Systems Development Method (DSDM) Scrum Crystal eXtreme Programming (XP)
Chapter 10 Information Systems Development. Learning Objectives Upon successful completion of this chapter, you will be able to: Explain the overall process.
 Son Nguyen, YM & Skype: ng_thanhson.
Chapter 2- Software Development Process  Product Components  Software Project Staff  Software Development Lifecycle Models.
Project Management Software development models & methodologies
Chapter 3 Agile software development 1 Chapter 3 – Agile Software Development.
CSc 171 Fall 2016 Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman 1 Chapter 12 – Multisite Projects How the customer explained.
CSc 171 Fall 2016 Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman Dilbert Scott Adams.
CS223: Software Engineering
Software Development - Methodologies
Dilbert – Management tips
Software Development Overview
Information about Life Cycles
Dilbert Scott Adams.
Appendix B Agile Methodologies
Dilbert Scott Adams Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman.
Chapter 10 Software Quality Assurance& Test Plan Software Testing
Software Development methodologies
PROJECT LIFE CYCLE AND EFFORT ESTIMATION
CS 425/625 Software Engineering Software Processes
V-Shaped SDLC Model Lecture-6.
Chapter 2 SW Process Models
Software Life Cycle Models
Chapter 2: Software Process Models
Dilbert Scott Adams Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman.
Software Processes.
Requirements and the Software Lifecycle
Johanna Rothman Start Somewhere Chapter 17
Software Development Process
Dilbert Scott Adams Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman.
Object Oriented Analysis and Design
Johanna Rothman Agile Team Measurements Chapter 12
How to Successfully Implement an Agile Project
Johanna Rothman Know What “Done” Means Chapter 11
A man is flying in a hot air balloon and realizes he is lost
Chapter 11 – Project Dashboard
Dilbert Scott Adams Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman.
An Overview of Software Processes
Dilbert Scott Adams.
Software & Systems Quality Conferences United Kingdom 2006
Software engineering -1
Gathering Systems Requirements
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
Software Processes Process should be
Chapter 2: Software Process Models
DSDM ArLinda A. Carroll.
Project Lifecycle and IT Product Life Cycle
Agile Development – a new way of software development?
Appendix B Agile Methodologies
The Waterfall Model Also known as: classic life cycle, the waterfall model, the linear model Rarely projects are sequential (allows iteration indirectly)
Gathering Systems Requirements
Agile software development
Chapter 11 – Project Dashboard
Software Development Overview
Presentation transcript:

Dilbert Scott Adams

Dilbert Scott Adams

Dilbert Scott Adams

…prerequisites I thought we had agreed long ago that the Department Policy was that all instructors would check for the completion of all prerequisites in the prerequisite chain. This may have been requested, but I don't recall it ever becoming policy. I don't check prerequisites. We are a 21st century computer science department at a university with an expensive CMS system. I would think that this is a university-wide problem and requires a university-wide solution that is better than having hundreds of faculty do such busy-work. Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman

  How hard would it be for CMS to make a second prerequisite check after grades have been submitted but before the semester begins? A few hours work by a talented programmer should suffice, don't you think? A day in the life… Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman

Chapter 3: Using Life Cycles “The way you and the team organize the work of product development.” “When… to define requirements, design, develop, and test, as well as concurrently.” There is no one right way… it depends. On what? Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman

What process? Evidence… shops that had no well-defined process were unable to deliver on-time with expected features. There is no “Best Practice” process. Necessary but not necessarily sufficient Every project is different, every team is unique… the Project Manager decides what works & what does not. The methodology chosen should include periodic reevaluation and inclusion of practices that fit your project and your team. Ship It! A Practical Guide to Successful Software Projects. Richardson & Gwaltney. Pragmatic Bookshelf, 2005 Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman

Figure 3.1 planned and occur. Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman

Figure 3.2 Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman

Figure 3.2 Completed features at the end of each iteration Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman

Figure 3.2 Completed features at the end of each iteration Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman

Figure 3.2 Completed features at the end of each iteration Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman

Combination: Iterative & Incremental Feedback needed: To assess remaining project risks To assess project’s state To assess how quickly the team can produce working software The more you know, the better you can predict “done”. Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman

Fig 3.7 One Large Project Life Cycle Developer Life Cycle Tester Life Cycle Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman

Feedback Design Debug Code Test Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman

Code & Refactor Loop Start a feature Test Code Refactor Build at least daily Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman

Architectural Risk Risk is that the architecture will not work for all features. Why would the Waterfall life cycle be the riskiest for managing architectural risks? “The only way to really manage architectural risk is to implement something and test it.” Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman

Stuck with a serial lifecycle! Plan to iterate on everything (planning, requirements & prototyping) Prototype and show your customer as much as possible as early as possible. Feedback!!! Integrate testing from the beginning… work with the testers. Implement by feature, integrating and testing… Documentation? Yes but not the deliverable. Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman

The author’s favorite Life Cycle Agile is her first choice… but!! If the customer is not readily available, If the team members are not “into” collaborating, If the team members are not disciplined, Forget it! Regardless, staged delivery is recommended. Finished features get pushed out as soon as possible. Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman

Staged Gate Idea Gate 0 Scoping Gate 1 Business Gate 2 Develop Gate 3 Testing Gate 4 Life Generation Case -ment Validation Cycle Building Mgt. Manage It! Your Guide to Modern, Pragmatic Project Management. Johanna Rothman