1 CMPT 275 Software Engineering Janice Regan, 2008-2014.

Slides:

Advertisements

Similar presentations

CMPT 275 Software Engineering

Advertisements

CSE101 Lab 3 Lecture Productive Team Work and Meeting CSE 101 Yinong Chen 1.

The Software Project Management Discipline Succes software projects require careful planning and good use of iterative approaches. Understanding risks.

The “Lifecycle” of Software. Chapter 5. Alternatives to the Waterfall Model The “Waterfall” model can mislead: boundaries between phases are not always.

Indistar: Updates, Additions, and Coming Soon Stephanie Benedict, ADI.

Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.

SWE Introduction to Software Engineering

SLIDE 1IS – SPRING 2004 Session 08: Project Plans IS Digital Media Design Studio Prof. Marc Davis UC Berkeley SIMS Tuesdays and.

0-1 Team # Status Report (1 of 4) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team #: Team Name.

0-1 Team # Status Report (1 of 4) Client Contact –Status Point 1 –Status Point 2 Team Meetings –Status Point 1 –Status Point 2 Team Organization –Description.

1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.

Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.

1 Chapter 6 Risk Management. 2 Project Risks What can go wrong? What is the likelihood? What will the damage be? What can we do about it?

Updating indicator implementation in Indistar Assessment Step Plan/Tasks Step Monitoring Step Flag to Re-assess.

Project Risk Management Risk Mitigation. Risk Management  The prime objective of risk management is to minimize the impact and probability of the occurrence.

1 CMPT 275 Software Engineering Revision Control.

Prepared for the Ottawa Region MISA Professional Network Centre - Summer 2006 Writing a Research Proposal for Funding An Overview.

[Insert Project Name] Preliminary Design Review (PDR) [Insert Date of PDR] Centers for Medicare & Medicaid Services eXpedited Life Cycle (XLC)

Paul Mundy Concept notes A brief summary of your project idea.

Chapter 3 Project Management

©Ian Sommerville 2006Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.

Software Project Management

Project Management Chapter 5, PG 92. Introduction Why is software management particularly difficult?  The product is intangible Cannot be seen or touched.

1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.

Why do Projects Fail?. Throw down single word / phrases why something doesn’t go to plan:

1 CMPT 275 Software Engineering Software life cycle.

Technology Programme Autumn 2005 Autumn 2005 Competition The Application and Assessment Process Peter Miles TUVNEL Ltd.

Moodle (Course Management Systems). Assignments 1 Assignments are a refreshingly simple method for collecting student work. They are a simple and flexible.

Travel Website Enhancement Project Project Update First Name Last Name.

Performance Planning & Evaluation Classified & Operational Form.

Software Project Planning Chapter 2 Applied Software Project Management, Stellman & Greene.

Tingxuan Liu Risk Management in Software engineering.

CMPT 275 Software Engineering

Project management Lecture 10. Topics covered Management activities Project planning Project scheduling Risk management.

Project Status Report Presenter Name Presentation Date.

Risk Analysis & Management

Project management.  To explain the main tasks undertaken by project managers  To introduce software project management and to describe its distinctive.

My Oral History Interview Insert Your Name Here Insert The Date Here.

1 CMPT 275 Software Engineering Requirements Analysis Phase Requirements Analysis activity Janice Regan,

© Janice Regan, CMPT 300, May CMPT 300 Introduction to Operating Systems Deadlocks II.

Introducing Project Management Update December 2011.

1 Identify Preferred Alternative and Finalize Plan Planning Steps 7 & 8.

Project Management. Introduction  Project management process goes alongside the system development process Process management process made up of three.

ECE791 Senior Design Experience Project Requirements and Timeline.

API 17N Subsea Production System Reliability, Integrity, and Technical Risk Management Don Wells Hess Corporation.

1 Two Places to Enter Time My Tasks (Project Plans, Proposals and Activity Plans) My Timesheets (Periods and Administrative Time)

[Project Title], #[Proj. ID] Lessons Learned Presented by [Name] [Date] Lessons Learned Template Version /07/2015.

1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.

Slide 1 CS 310 Ch5: Project management What do you think is involved? Proposal writing Project costing Project planning and scheduling Project monitoring.

Fall CS-EE 480 Lillevik 480f06-l7 University of Portland School of Engineering Senior Design Lecture 7 Functional specifications Technical meetings.

NEW GRANTS MANAGEMENT ENTERPRISE (GME) Completion Reports and Applications.

Improving Client Engagement in Primary Health Care Services Jewish Guild For The Blind.

Comprehensive Continuous Improvement Plan(CCIP) Training Module 4 Funding Application.

Risk Mitigation Submitted By, S. Anitha Devi, M.E-CSE.

Risk Assessment Meeting

<workgroup name>

Risk Lab Exercises.

QUALITY IMPROVEMENT [SECOND]/[THIRD] QUARTERLY COLLABORATIVE WORKSHOP

SCC P2P – Collaboration Made Easy Contract Management training

QUALITY IMPROVEMENT FINAL QUARTERLY COLLABORATIVE WORKSHOP

Risk Register I want to plan a project

STEP 8 - CLOSING PHASE: TRANSITION SUPPORT

Assessing Risk Impact Factors affecting the consequences Nature Scope

DTE Fall 2018 – Directors Presentation

Bourke properties Houston, Whitney relocation info 23/02/2019.

Invitation Cards.

General recommendations

Studio day : Friday (page 1 of 2)

QBR Commodity Name Supplier Name QQ YYYY Precise your commodity name

Project Overview.

Presentation transcript:

1 CMPT 275 Software Engineering Janice Regan,

2 Example of Revision History RevisionStatus Publication/Revision Date By: 1.0Created, May Revised (Specify which section(s) of the document was (were) revised and why), May Final Revision (Specify which section(s) of the document was (were) revised and why), Jan

Janice Regan, Example of Revision History RevisionStatus Publication/Revision Date By: 1.0Created Wednesday May Su Jo Steve Sims Jan Jones 1.1 Section 4 added Section 2.3 updated to include new hardware information Wednesday, May Steve Sims Jan Jones 3.0 Final Revision, to be released with V4.2 of product. Sections 5 and 6 added Section 2.8 and 3.2 revised Tuesday, Jan Su Jo Kumar Smail

Revision History  Each document you create will have its own revision history.  Groups of small changes can be inserted together as one revision.  Always indicate every section that has changed in the revision history  Give very brief descriptions of each set of changes (examples on previous 2 slides) Janice Regan,

5 Risk Analysis  A risk is a potential problem that would hinder the progress of an activity/project if it were to occur.  To identify risks need to ask: What could happen that would make our project late?  Mitigate identified risks by making plans that detail how to avoid the risk or recover from the risk

Janice Regan, Action Plan A set of steps that eliminates risk before the activity/project commences. What When Before the risk occurs!

Janice Regan, Contingency Plan A set of steps that reduces the impact of risk once it has occurred during an activity/project. Wha t When

Janice Regan, Risk Analysis  Let’s consider an example:  We are planning an awards dinner for a the participants of a programming competition.  What can go wrong?

Janice Regan, Consider our example  Not enough food for all the participants.  Action Plan 1: Estimate the maximum number of attendees and order food for that many people.  May be expensive if not all participants attend

Janice Regan, Consider our example  Not enough food for all the participants.  Action Plan 2: Send invitations with an RSVP. Order enough food for those who reply, plus a small additional amount (some may come even if they did not reply)  Will better estimate the amount of food needed  OTHER SUGGESTIONS?

Janice Regan, In Class Exercise  Choose a partner  Discuss your term project  Identify some risks  Provide a contingency plan to mitigate one risk  Provide an action plan to mitigate one risk  Turn in 1 page with a summary of your risks and plans. I will mention some of them at the start of next lecture. (after the team meeting)