Project Management Project planning individual assignment: Project CLOCK

Slides:



Advertisements
Similar presentations
Homework 3 Solution Lecture Packet 16 © John W. Brackett.
Advertisements

Software Quality Assurance Plan
Chapter 3 Project Initiation
Software Delivery. Software Delivery Management  Managing Requirements and Changes  Managing Resources  Managing Configuration  Managing Defects 
1Lou Somers Software Engineering Projects 2IP35 Autumn 2014
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 2 Software Processes.
Modern Systems Analysis and Design Third Edition
Project Time Management
Project Management Session 7
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
Senior Design – Acceptance Test Plan Review The goal is to: define the criteria for approving the application. Tightly coupled to the Requirements document.
LSU 10/09/2007Project Schedule1 The Project Schedule Project Management Unit #4.
Development and Quality Plans
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
ADDIE Instructional Design Model
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
Project Management Software Tools Cheryl A. Wilhelmsen Lee Ostrom.
Release & Deployment ITIL Version 3
IT 499 Bachelor Capstone Week 9.
Systems Analysis and Design in a Changing World, 6th Edition
Initiating and Planning Systems Development projects
ADDIE Instructional Design Model
COMPGZ07 Project Management Presentations Graham Collins, UCL
ERP Lifecycle.
Contractors & contracts
Project Management Development & developers
Project Management Project Planning Costs & Budget
Common PDR Problems ACES Presentation T. Gregory Guzik March 6, 2003.
Project Management : Techniques and Tools (60-499) Fall 2014 / Winter 2015.
K-12 Web Content Development Process
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Recap from last week Understand organizations, including the four frames, organizational structures. Explain why stakeholder management and top management.
Next Doc Project Team: xxxxx Spring TitlePage Scope Statement Mission Statement3 Business Need4 Project Description5-6 Project Lifecycle Approach7.
IT Project Management Tools Available for Use at the Utah Dept. of Health The sooner you begin coding the later you finish. What is not documented has.
Work Breakdown Structure (WBS) Development
ECTL A Support to the Automated Safety Data Monitoring Indicator project.
BSBPMG505A Manage Project Quality Manage Project Quality Project Quality Processes Diploma of Project Management Qualification Code BSB51507 Unit.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Product Tracking Database Sponsored by Aviation learning, Inc. The goal is to create an n-tier, client-server system that will track the product and order.
Introduction to Systems Analysis and Design
© Mahindra Satyam 2009 Configuration Management QMS Training.
Systems Life Cycle A2 Module Heathcote Ch.38.
Online Tech Support Web Forum For F.B.I.S.D By: Team X-Velocity.
PLANNING ENGINEERING AND PROJECT MANAGEMENT By Lec. Junaid Arshad 1 Lecture#03 DEPARTMENT OF ENGINEERING MANAGEMENT.
Pre-Project Components
PRJ566 Project Planning & Management Work Breakdown Structure.
Workforce Scheduling Release 5.0 for Windows Implementation Overview OWS Development Team.
Project Initiation at The Regence Group 12/19/2015John Garrigues1.
Phoenix Campus Faculty Refresher Training. This workshop will provide faculty with updated knowledge and tools necessary to be effective in the classroom.
Requirements Document Work Breakdown Structure. Schedule DateTooicAssignment 1-Oct-08work breakdown/features breakdown 8-Oct-08agile methodsrequirements.
ECE791 Senior Design Experience Project Requirements and Timeline.
Thomas Kern | The system documentation as binding agent for and in between internal and external customers April 24th, 2009 | Page 1 The system documentation.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Tyler Implementation Kick-Off Aaron Joyal, PMP Financials Project Manager.
1 Chapter 11 Planning. 2 Project Planning “establishing a predetermined course of action within a forecasted environment” “establishing a predetermined.
Z26 Project Management Presentations Lecture 5b 9 th February 2006 Graham Collins, UCL.
Component D: Activity D.3: Surveys Department EU Twinning Project.
Project Management Testing & Acceptance
Project Management Software development models & methodologies
Retailer Enrollment Process
Ganaxa case study & assignment:
Project Management Case study & Assignment:
Managing the Project Lifecycle
Systems Implementation,
Systems Analysis and Design
End of Year Performance Review Meetings and objective setting for 2018/19 This briefing pack is designed to be used by line managers to brief their teams.
Lesson 1 Understanding Software Quality Assurance
Brainstorming & Project Management
Studio day : Monday February 4
CMGT 410 HOMEWORK best future education / cmgt410homework.com.
Presentation transcript:

Project Management Project planning individual assignment: Project CLOCK

Project CLOCK – Context (1) Company X (which is based in France) needs to train its staff and business partners on a very frequent basis in order to keep them up-to-date on its products, services and operations processes, which are in constant evolution. Most of the training is done online via an existing web- based e-Learning platform. All courses and training tools are created in-house. You are a Project Manager in the e-Learning Production department of this company. PM

Project CLOCK – Context (2) The head of the e-Learning Production department has identified the need for a set of tools/templates that will enable instructional designers/writers to easily build a broad variety of "learning objects". Existing tools/templates are considered unsuitable. The department head wants new tools to be created. He has provided summary requirements, schedule & cost constraints, and has designated the people who will work on this project (code-named CLOCK*). You have been given the responsibility for leading the project team that will create such tools. PM HD € * Creation of a Learning-Object Construction Kit

Project CLOCK – Resources * Head of Department (project sponsor) Project Manager (You!) HD PM IW1 IW2 SD1 Instructional Designers/Writers D Software Designers/Developers SD * No more, no less! (All 6 people are employees of company X.) €

Project CLOCK – Work done & Work to do You have held a 3-day brainstorming meeting with the 2 IWs and the 2 SDs to produce and agree upon a comprehensive and detailed Requirements Specification for a "Learning-Object Construction Kit" made of 10 different tools/templates, as well as a data delivery format, and to evaluate the work to be done. (The HD has approved the final Requirements Specification.) You must now establish a project plan to present to the HD. The plan must cover everything to be done following the agreement on the requirements, ie from design to deployment and project closure, and it must clearly show the project schedule and cost. DONEDONE TODOTODO

Project CLOCK – WBS Design Sample data preparation & delivery Project management Testing, bug fixing & acceptance Deployment Perform functional & UI design Review & agree upon design PrototypeFinal version Project closure Perform technical design for the learning-object construction kit Software coding Test case preparation Review design after prototype acceptance, agree on changes to be made, make technical design changes Prototype Final version Delivery of software for testing PrototypeFinal version

Project CLOCK – Resource assignment Participates in design reviews and agreements Participates in final testing/acceptance of prototype & final version Performs overall project management (50% of her/his time) HD PM IW1 IW2 SD1 Participate in functional & UI design Participate in design reviews and agreements Perform sample data preparation & delivery Prepare test cases; perform tests of prototype & final version Participate in final testing/acceptance of prototype & final version SD2 + All 6 people participate in project closure Participate in functional & UI design; do technical design/redesign Participate in design reviews and agreements Implement/code software and fix bugs revealed by tests done by IWs Deliver software for testing by IWs (and by PM for the final version) Deploy final version on "production" server €

Project CLOCK – Assumptions (1) Sample data (for the 10 different learning-object creation tools/templates to be developed) prepared by the IWs is required by the SDs before the beginning of the prototype software coding (not design) phase. Delivery of sample data can be treated as an implicit task of "Sample data preparation & delivery". There is no need for "final data". Graphic design of the UI is relatively simple and is done by the SDs as part of their development work. Such graphic design work does not need to be made explicit in the plan.

Project CLOCK – Assumptions (2) SDs may (should!) test their software before delivering it for testing by IWs, but such "internal tests" can be kept implicit in the software implementation/coding tasks. Delivery of prototype software and delivery of final software for testing must be explicit tasks in the plan. Testing by IWs is followed by bug fixing by SDs followed by final testing and acceptance (without further bug fixing) by IWs and the PM. This "simplified cycle" applies to the prototype and to the final version of the software. Test cases are written only once (they are valid for both the prototype and the final version of the software).

Cost of HD's participation not to be counted No other costs to be taken into account Project CLOCK – Cost assumptions € 450 / day PM IW1 IW2 SD1 SD2 € 360 / day € 330 / day € 420 / day € 400 / day

Project CLOCK – Constraints Start date = January 4, 2016 Total duration no longer than 7 weeks Duration unit = day (not hour) "Standard" number of hours (8) per working day 5-day weeks (no work on weekends) Public holidays not taken into account Nobody (incl. the PM) to be loaded more than 100%! Total cost (budget) no greater than € 45,000 (end date no later than February 19, 2016)

Now, to make your assignment easier…

Download plan to complete from… neil.minkley.fr/epita May be useful…

Project CLOCK – Plan to complete (.mpp) Will be (re)calculated automatically by the software ?? Durations at the lowest level should have the same values in the completed plan as they have here.

Project CLOCK – Plan to complete (.pod) ?? Will be (re)calculated automatically by the software Durations at the lowest level should have the same values in the completed plan as they have here.

 Send your completed ".mpp" or ".pod" file to before Tuesday December 15, 2015 after changing the prefix of the file name to an unambiguous NAME that clearly identifies you, for "Neha_PRABHU_ CLOCK_PLAN.mpp", not "PRABHU_ CLOCK_PLAN.mpp"  Imagine YOU are the PM for this project!  Take into account the relevant information given on the previous pages of this document.  Download & complete the project plan (.mpp/.pod file): 1)enter appropriate "Predecessors" information, featuring parallelism between tasks whenever possible, 2)enter appropriate "Resource Names" information. using Project 2013 or ProjectLibre Note: failure to meet the deadline will result in a 0 (zero) grade! Project CLOCK – Assignment Note: you may need to adjust durations at the lowest level of the WP/task hierarchy to their initial values. PM

Questions?