Grades and Class Structure
Grades
This class is offered Wednesday evenings. If you cannot make it. Each weekly lesson's practice session will be turned in to me at the end of class. If you miss a class it is YOUR RESPONSIBILITY to make up that practice session and turn your document in to me by the following week. Since all materials are available online, you can easily follow the course materials. These weekly assignments make up about 50% of your final grade
|
|
CIS 214: System & Software Requirements
This is the course outline for your Syllabus.
See the Deliverable
May 2013
Instructor: Myra Anson Nicholas
Email: coyote@nanosite.com
Cell: (703) 402-9065
Classes: Wednesday 6pm
ELEMENTS THAT PRECEDE THE PLANNING PHASE: These are key to IT Project Success
- Project Concept and Definition
- Which Yields Requirements Identification
- Requirement specifications describe deliverables
- Defines format and characteristics of deliverable
|
- Risk Management: probability/impact
- Quality Management
- Scope Definition (change control)
- Software Prototyping
- Documentation/Configuration Management System
|
|
WE INTERRUPT THIS BROADCAST FOR A ....
Ok, i still haven't gotten into moodle, but have set up a "catch-up" plan that will be in compliance with the "learning outcomes"
Ok, Here’s the details of what we will need to do to conform to the school’s rules: (if you prefer to read the word document, it is here
For each week of class:
- I have to give an assignment that will be posted on moodle, so it is documented.
- I have to create a discussion topic that all students must respond to through the moodle discussion board.
- I have to assign research and reading for student response (like the exercises)
- We will now assume that the “board game” is a web-based software game. (you’ll be using the same visuals… I’ll be giving you platform and software suggestions… and I’d be surprised if some of you didn’t go ahead and do it… it can be as simple as you make it)
I will just list what needs to be done, then detail below the why and wherefore.
So here’s our “catch up”
Part 1 is Planning
Required: Chapter 1 of the book discusses gathering and analyzing requirements. (by the way, a quick read on p 35 of the exercises is interesting)
Already Done: You gathered the project charter, and
identified the types of deliverables by determining details of the game.
What you need to do: You already interpreted my scope into actual requirements, so you need to:
- Set a goal and use the Requirements Document I set up to lay out the initial requirements as you understand them, note that i have filled out all but 3 columns.
- Write a requirements specification (page 2 of same doc) for this project
- List the key objective
- Describe the environment the system will work in.
- Note any questions or inconsistencies you find when writing your Requirements Document (this is expected)
- Note requirements that are not actual deliverables, but are customer “needs”
Read notes at the bottom of the document after done.
Below are things you need to read (short)
- Understand pitfalls: (see pg 23)
- The requirements specification often becomes the sole deliverable
- And critical information you need to know (which you will need to understand) below which Ghada considers a vital part of this process: (I will post these rules on moodle)
2. Your WBS (They Call It Task Analysis)
Required: Please clean up your WBS and transfer it to the new template using your original
Already Done: You already started (and probably finished) the WBS, and have it ready.
What you need to do: If you have not already done so,
- The project needs to be broken down into major deliverables,
- then further into secondary tasks
- Indicate where the task needs to be broken down further
- Indicate the sequence of the tasks
- If you can do it, then fill in the appropriate “keys” I’ve used to indicate the level of effort required.
- Indicate (using asterisk) areas that involve risk (risk can be software, resources, time, anything that can derail the project)
I set up 2 WBS documents… one for the top level, and another for the detailed one... but you do not have to fill out #2
3. The Resources Matrix… and the Risk Analysis
Required: DO NOT fill out the Resource Responsibility Matrix but study the combined resource matrix form.
Required: Do address the New Risk Analysis and Planning Form.
Using your WBS, choose a few likely areas where risk may occur. You can choose from the Risk Source box at the bottom to create at least 3 risks, then create a realistic situation and a logical solution.
4. There is a new QUALITY REVIEW MATRIX FOR PLANNING PHASE
I will email this when it is finished, but I wanted you-all to get this asap.
And finally, we will cover project metrics, goals and measurements (chapter 3) and if you’ve really read this far, I will be bringing fireworks (not terribly legal in VA, so you can take them home and have fun blowing off a finger) M-80’s and whatever else I can find from our big buying trip to NC a while ago.
that's all folks
|
Class 2
Project Management Glossary From Project Smart, UK
Project Management Glossary from Wikipedia
Wideman Comparative Glossary of Project Management Terms |
|
ESSENTIAL PROJECT MANAGEMENT DEFINTITIONS, ROLES AND CONSTRAINTS
Topic: Review of the badly-illustrated, but well thought out review of project management (and yes, here's their own description "a fun edutoon series on project management — things you should know but may have forgotten.") by Max Wideman, whose site is excellent, but this presentation... not so much.
Understand the basic constraints:
of Scope, Cost, Time now evolving to Risk, Quality, Resources:
their application to the roles of the Client, the Project manager and Upper Management.
Homework: Review key PM processes:
risk analysis/management: (chapter 5, textbook); ePMbook*; Risk assessment tool from Leading Answers
Risk Planning Worksheet Quality Management: Quality Management vs Quality Audit
Scope (and change)Scope and Change Control, Chapter 15, textbook: change control
Documentation/Configuration Management System: Chapter 7, textbook, Processes p. 145;
|
Deliverable: Project Management Simulation Board Game
THE REALITY PROJECT: OH BABY, WHAT A DELIVERABLE!
An 8” wide project gameboard graphic is at the end of this document. This is to help you iand further explain my concept of the deliverable.
Much like the game of life, i see this as a game of project. We’ll discuss the best way to do it, but as of know i think we’ll consider it a team game, with each “player” a team.
Since we need to split this up, there will be 2 phases: The planning Phase and the Implementation Phase. The Midterm will be where you turn in your prototype and planning documents, which i expect to be rough, not perfect, but will illustrate your thnking.
The Final will be a nice clean version, just as you’d present it to a board game or computer game company. I may be able to do a web version given time. Download the entire explanation here.
Classes 3-5 will be all project planning - leading to Midterm prototype and Planning Document
|
Class 3
|
|
PLANNING: (WBS MODEL), SCOPE
ROLE AND RESOURCE PLANNING
Topic: Using either the WBS model, or one of many other models, the defined deliverable has become our scope. From this scope an experienced project manager defines the shape of the project. Waterfall, overlapping phases, iterative
IN CLASS EXERCISE: As a class we will talk out the scope of the deliverable, the prototype, how it is to be presented for final deliverable, and methodology for testing individual student performance.
IN CLASS GROUPS: Start developing a Project Plan from initial scope. You are in the project planning phase:
RESOURCE WORKSHEETS: The "Foundation" of Project Planning. The WBS is defined as: "A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables."
Sample Work Breakdown Structure. Project WBS
Articles: Creating a Work Breakdown Structure (WBS) By Tony Jacowski
Work Breakdown Structure: Purpose, Process and Pitfalls by Micah Mathis, PMP
Work Breakdown Structure Made Easy By Mohammed K Barakat
Homework: Students will continue development of planning document, each group determines roles. Note Each student will create their own "logbook" in which they record lessons, learned, concepts and ideas (used or not used for this class), notebooks may contain worksheets. These notebooks will count towards your final grade (and highlight areas to focus on)
|
TEAMS
|
|
Team 1 (Doc emailed to me)
David Parker
Terrence Sullivan
Claude Bernard
Nichole Allen |
Team 2 (Doc emailed to me)
Rodney Shields
Meriem Yoghmmour
Stephan Porter
Demetrius Haynes |
Team 3 (Doc emailed to me)
Aaron Lattin
Samuel Hillman
Tajh Smith
Dustin Atienza |
ALL TEAMS ARE RESPONSIBLE FOR THE MIDTERM. THE SCOPE IS IN THE PROJECT CHARTER:
First phase of Project management is to complete the project charter. In the last class we laid out the Objective and Scope. Your next task is to start identifying the elements that have been left for each team, then start creating a Work Breakdown Structure. (see Class 3 for details on how to do a WBS and samples)
Objective: Create A Project Management Simulation Board Game
Scope:
The board game simulates the planning and implementation phases that a project manager works through in creating a project. Players are team, but move token individually on the board: (Team can play against team)
- 1 member represents management (resources, hr, legal,)
- 1 member represents the project manager
- 1 member represents the customer
Team can determine board game layout but ½ is planning and ½ is implementation
Team writes event cards: minimum 12 for planning, 12 for implementation
Team uses community inbox cards to write reward cards (time/money/resources)
The Project Charter link is here
Work Breakdown Structure. Example WBS
Example of simple WBS (high level)
Excel WBS Template I set up for you to use.
|
|
Class 4
|
|
PLANNING: RESOURCE AND QUALITY MANAGEMENT, RISK MANAGEMENT
IN CLASS EXERCISE: Continuing with the planing phase, we will review how resources and quality impact risk. Guidance on Risk Management
IN CLASS GROUPS: Continue with project planning phase Quality, Resource and Risk Management;
Resources: (PMBOK and Other PM Worksheets ) Review and use samples: (click to download)
Requirements Tracability Matrix
Risk Planning Worksheet
Resource Responsibility Matrix
Checklist for Scheduling Projects: Project Schedule Key Elements
Reading:
A Word (Or Two) On Quality By Gina Lijoi
One of the worst mistakes a project manager could make is to complete testing themselves.
Flawless quality assurance is an expert skill that is developed over time. Like project managers,
professional testers will have solid process and methodology to support their efforts. When time
and budget are running out, some project managers will take on the quality assurance portion
themselves, thinking a quick review will suffice - this is never the case. Leave testing to
professionals-facilitate the process, but don't overtake it if you intend on delivering a perfect product.
Homework: Students will continue development of planning document, each group determines roles. Note Each student will create their own "logbook" in which they record lessons, learned, concepts and ideas (used or not used for this class), notebooks may contain worksheets. These notebooks will count towards your final grade (and highlight areas to focus on)
|
Class 5
List of documents essential to Project Management: PLANNING
Project Charter
WBS
Risk Planning Worksheet
Resource Responsibility Matrix
Quality Review Plan Checklist
Phase Sign-Off
IMPLEMENTATION
Communications Matrix
Skills Matrix
Scope Change Request
Lessons Learned
Quality Review Checklist
|
|
PLANNING: CREATE TEAM, TASKS FOR TEAM ROLES (RESPONSIBILITY MATRIX) SET MILESTONES
IN CLASS EXERCISE: Continuing with the planing phase, we will review how resources and quality impact risk. Guidance on Risk Management
Logical Process of Entire Project Management Process (use for Game as well)
IN CLASS GROUPS: Continue with project planning phase Team Building, Responsibilities, Roles;
PLANNING
- PM given the scope of the project
- PM review scope and questions/refines areas in question
- PM takes entire project and brakes it into top-level deliverables
- PM breaks down each top-level deliverable into distincitve tasks (Requirements Tracability Matrix keeps track of the individual tasks) as further breakdown is required (milestones noted)
- PM (with staff) reviews deliverable and lists areas/tasks/attributes that represent a risk:
-for additional resources to perform
-that may impact schedule
and assigns their level and notes the best response..(how they should be handled)
- PM documents the planning process and recaps what was done
- PM Lists all the resources that he/she determines is necessary for this project by task.
|
|
IMPLEMENTATION
- PM Assembles team, and assess the skills necessary
- PM reviews project schedule sets milestones, meetings & reports
- Risks are prioritized, and addressed as they come up
- As project is in implementation phase, any change to original scope triggers a scope change request.
- Before final quality review, note is made of lessons learned from project
- Final quality review before sign-off
|
Resources: (Use word documents on the left side)
Teams: (click to download full size):
Risk Planning Worksheet
Resource Responsibility Matrix
Setting Milestones 
Project Planning Resources
Developing Project Schedule (part 2 in the Project Lifecycle from the PM Hut Website - contains wbs, activity, network diagram, and activities).
Project Planning Chapter from GSAM:
IN CLASS AND HOMEWORK:
Risk Planning and Resource Responsibility
Review Phase Sign-Off sheet! |
REVIEW "PROTOTYPE" (ROUGH DRAFT) OF DELIVERABLE w/IMPLEMENTATION PLAN
Accompanied by "THE QUALITY REVIEW MATRIX FOR PLANNING PHASE (MYRA'S VERSION)" from each class member.
|
Class 6
|
|
IMPLEMENTATION: A COMMUNICATIONS PLAN
Topic: A Communication Plan provides a framework to ensure successful execution of the
project. This Matrix details meetings and reports, as well as attendees.
Review Team Communications Matrix
REVIEW "PROTOTYPE" (ROUGH DRAFT) OF DELIVERABLE w/IMPLEMENTATION PLAN
Accompanied by "THE QUALITY REVIEW MATRIX FOR PLANNING PHASE (MYRA'S VERSION) " from each class member.
Homework: You may revise your matrix.
|
Class 7
|
|
IMPLEMENTATION: ASSESS JOB SKILLS AND , PROJECT SCHEDULE, RISK PRIORITY
In class-exercise: Fill out details using Key Elements Checklist: Project Schedule Key Elements
Create skills list for team and match up with resources you have. Use the Skills Matrix
And review schedule with your Risk Priroity Checklist for conflicts.
Review
Midterm Doc Quality Review Plan Checklist
Homework: .
|
Class 8
|
|
MONITORING: SCOPE CHANGE
Topic: Project Management Process Quality Review: Execution and Control Phase:
Evaluating the Project management process is critical to determining where changes or
improvements are needed. Use this checklist periodically throughout the project
lifecycle to assess how well the project is progressing.
IN CLASS EXERCISE: Scope Change Request AND Scope Change Control Log
Homework:
|
Class 9
|
|
TEAM MANAGEMENT, STAKEHOLDER MANAGEMENT, SCOPE VERIFICATION
Topic: Presentations of final Deliverable for class and customer review
IN CLASS EXERCISE:
Homework: Make any change to presentation requested
|
Class 10
|
|
CLOSEOUT AND LESSONS LEARNED
Topic: Presentations of final Deliverable
|
|
|
| |
Hints, Tips, Shortcuts & Time Savers
This area dedicated to hints, tips and more to enhance your project management skills.
Project Management LinksWikipedia's definition: Project management is the discipline of planning, organizing, motivating, and controlling resources to achieve specific goals
Traditional approach
Project Management Definitions from The Project Management Institute one of the world’s largest not-for-profit membership associations for the project management profession. Publications referenced in this syllabus:
All About Project Management from the Free Management Library
The ePMbook is double-e'd. It is an ebook about eProject Management as well as conventional Programme and Project Management. Its aim is to examine issues, needs and approaches in a variety of situations and environments. It should give you the ability to understand what is needed and why, plus how you can best address those needs.
Very chatty, deals with IT project management, and gets into tracking, estimating, reporting, support roles Project Management Book www.hraconsulting-ltd.co.uk
More info
Informative links and Good Info
Wed., June 26
Great piece on NPR's The Kojo Nnamdi Show (you can listen to it from the website)
Rethinking Higher Education
Today at 1:06 p.m.
... Kojo talks with the editor of the Chronicle of Higher Education, Jeff Selingo, about the real value of a college education and the future of the higher education system.
How Long Should A Software Project Take?
Max Wideman and other weigh in on this fascinating thread that was started by a question "Are there any tools/formulae to estimate the proper and practical schedule for a software development project, given that the total effort is known?" links to responses from experts in the field.
|