Docstoc

LINDA REED

Document Sample
LINDA REED Powered By Docstoc
					Web Project
CS632 Team 2
William Carron, Patrick Dwyer, Joong Lee, Linda Reed, Arjun Vyas and Aaron Wong

1    BUSINESS CASE.................................................................................................................. 4
2    PROJECT CHARTER ......................................................................................................... 5
3    TEAM CONTRACT ............................................................................................................. 7
4    SCOPE STATEMENT ......................................................................................................... 9
5    PROJECT PLAN ................................................................................................................ 14
  5.1   Purpose/Background/Approach .....................................................................................14
  5.2   Goals and Objectives .....................................................................................................15
  5.3   Constraints/Assumptions ...............................................................................................16
  5.4   Related subprojects/critical dependencies .....................................................................18
  5.5   Web Project WBS MS Project > Visio .........................................................................19
  5.6   Schedule and Milestones (MS Project) ..........................................................................20
  5.7   WBS (MS Project) .........................................................................................................20
  5.8   Tools and techniques......................................................................................................20
  5.9   Budget for Hosting .........................................................................................................21
6    RISK MANAGEMENT...................................................................................................... 21
  6.1   Risk Identification ..........................................................................................................21
  6.2   Quantification ................................................................................................................24
  6.3   Mitigation .......................................................................................................................24
  6.4   Contingency Plan ...........................................................................................................25
7    QUALITY, MANAGEMENT CHANGE AND CONTROL PROCEDURES.............. 26
  7.1   Title Page .......................................................................................................................28
  7.2   Privacy Information .......................................................................................................29
  7.3   Introduction ....................................................................................................................29
  7.4   Purpose...........................................................................................................................29
  7.5   Scope ..............................................................................................................................30
  7.6   Background ....................................................................................................................31
  7.7   Project Checkpoints .......................................................................................................31
  7.8   QA/QM Roles and Responsibilities ...............................................................................32
  7.9   Senior Management .......................................................................................................34
  7.10 Web Project Task Leader ...............................................................................................34
  7.11 Quality Assurance Team ................................................................................................34
  7.12 Technical Staff ...............................................................................................................35
  7.13 Required Skills ...............................................................................................................35
  7.14 Quality Assurance Procedure .........................................................................................36
  7.15 Walk Through Procedures .............................................................................................36
  7.16 Review Standards...........................................................................................................37
  7.17 In stage Assessments......................................................................................................37
  7.18 Stage Exits .....................................................................................................................41
  7.19 Peer Review ...................................................................................................................45
  7.20 Audit Process .................................................................................................................45
  7.21 Audit Procedure .............................................................................................................46
  7.22 Evaluation Process .........................................................................................................47
  7.23 Process Improvement .....................................................................................................47
  7.24 Problem Reporting Procedures ......................................................................................48
  7.25 Non Compliance Procedures..........................................................................................48
  7.26 Quality Assurance Management Plan ............................................................................49
  7.27 References ......................................................................................................................49
8    HOW OUR TEAM MANAGED CHANGES AND SCOPE CREEP ............................ 50
9    PROJECT NOTEBOOK.................................................................................................... 50
  9.1   Roles and Responsibilities .............................................................................................50
  9.2   Team Blog ......................................................................................................................51
  9.3   Team 2 Website .............................................................................................................51
  9.4   Team Contact Directory.................................................................................................51
10 TEAM MEETINGS ............................................................................................................ 51
  10.1 Week 3 Kick-Off Meeting .............................................................................................51
  10.2 Week 4 Team Meeting ...................................................................................................55
  10.3 Week 5 Team Meeting ...................................................................................................60
  10.4 Week 6 Team Meeting ...................................................................................................70
     10.5 Weekly Status Report Week 3 thru 6 are contained in the meeting sections ................80
11     TECHNICAL DOCUMENTATION ................................................................................ 80
     11.1 Technical Specifications ................................................................................................80
     11.2 Technical Objectives ......................................................................................................80
     11.3 Site Overview.................................................................................................................80
     11.4 Hosting ...........................................................................................................................81
     11.5 Site Map and User Manual ............................................................................................81
     11.6 Flow Chart .....................................................................................................................87
     11.7 Database Schema ...........................................................................................................88
1   BUSINESS CASE

Introduction/Background
Boston University Metropolitan College Project Management department provides conferences throughout the year. Vijay Kanabar,
Project Management professor believes the Project Management web site can provide the department more useful information than
just registering potential conference attendees name and e-mail address.

Business Objective
Boston University Metropolitan College Project Management department want to enhance the functionality of the website. The
updated website will support the goals of enhanced functionality by providing a dynamic place for potential conference attendees to
enroll in a conference and providing a place to display the work of select Project management students.

Current Situation and Problem/Opportunity Statement
Boston University Metropolitan College Project Management department has a public webpage on the Internet. The project
management department uses the webpage to advertise upcoming conferences related to project management topics. The functionality
of the website is limited because potential conference registrants are only able to place there name and e-mail addresses in to the
database. Once in database, department staff need to attend to contacting registrants concerning there level of interest in the
conference. The problem is potential conference attendees my not attend a conference because there is no commitment on their part. It
is time consuming for project management staff to contact and follow up with web site enrollees.
Currently, there is no place on the web for project management faculty and student to display their work. There is the opportunity to
upgrade the functionality of the site to take payments and/or deposits of potential conference attendees. This will allow project
management conference organizers the ability to forecast who is really interested in attending the various conferences. Increasing
functionality will automate data collection and reporting from the conference attendee database freeing time of department staff to
attend to other issues. Increasing the functionality of the web site allows for a forum for student and faculty to display their work
including sample PDF’s files, selected abstracts, pod casts and video casts.

Critical Assumptions and Constraints
The Boston University Metropolitan College Project Management department must actively update the content of the website to keep
it relevant to current department events. The new system must be hosted by a web site hosting company. The site must be easily
accessible to the public and must be secure from unauthorized access.
Analysis of Options and Recommendations
There are three options addressing this opportunity

    1. Do nothing. The current website can continue to perform with its limited functionality.
    2. Develop system that performs web based conference registration and provides a link to team members abstract paper and pod
       casts from the Research.htm
    3. Develop “fully functional system” that includes functionality from #2 above with additional functionality of private login for
       project management department administrative staff to see conference participants, shopping cart functionality for deposits and
       payments from conferences participants, and Pod cast or Video Cast of student abstract articles.

Budget Estimate and Financial Analysis
A preliminary estimate of costs for the entire project is $310.80 for two years of web hosting at $12.95 per month. The development of
the site is performed by student for no cost. Web site monitoring and content update is performed by current project management web
master and no additional cost to this project.

Schedule Estimate
The sponsor would like to see the project completed within six weeks. There is no flexibility with the schedule but there is flexibility
with the level of functionality of the website.

Potential Risk
There are several risks involved with this project. The primary risk is we are limited to one developer on the project team who can
build the website functionality. Secondary risk is that there is not enough time in the semester to deliver a fully functional system.
Tertiary risk includes security of the website from intruders gaining access to conference enrollee’s personal data.


2   PROJECT CHARTER

Project Title: Web Project
Project Start Date: May 22, 2006             Projected Finish Date: 21 June 2006
Budget Information: The school has allocated $1,000 for hosting and development and $12.95
monthly hosting fee.
Project Manager: Linda Reed
Project Objectives: Develop a new automatic registration system for Boston University’s
annual Project Management Conference eliminating the email system by building a database to
store conference registration to allow the conference chair to print the data dynamically
utilizing the existing website http://www.bu.edu/met/news/project_management/. The project’s
second objective is to enhance the Boston University CS632 research page at http://www.bu-
pm.com/cs632/research.htm to provide PDF files, selected abstracts, podcasts and videocasts
from students and faculty research. These new features will augment the existing project
management website by providing visitors the opportunity to register for the annual Project
Management Conference. The Boston University’s CS632 research site will showcase the
student and facility’s research by videocast and to podcast conference papers. Other
specifications could be provided as the website is being built.
Approach:
      Develop a survey that describes the known features of the registration site to include the
        administrators’ page to be password protected and to validate that the research page is to
        be classified by topics and confirm these requirements with the sponsor and
        stakeholders. Solicit inputs from the stakeholders Dr. Kanabar, Roxolana, Director of
        Marketing, Damian Ross, IT and Web Architect, and Facilitators Donald Buresh or Fred
        Santino as needed.
      Review templates and examples of project management documents that will best
        facilitate our web project.
      Research database, videocast and podcast software capability that will interface with
        existing software.
      Develop the intranet using the waterfall approach, soliciting a great deal of user
        feedback.
      Determine a way to measure the value of the new Project Management website and
        quantify how the students and facility will benefit from the enhanced research page.
      The team will setup the free conference call phone service and commit to a time that is
       convenient for all to communicate and discuss project phases, phase exits or possible
       kill points on a weekly basis.
    Discuss the option to setup a team blogspot or communicate thru WebCt.
    Identify and coordinate the work breakdown structure (WBS) efficiently to meet the
       project deadline and to allow enough wiggle room if problems are anticipated during the
       web project development.
Roles and Responsibilities:
Name                Role                  Position               Contact Information
Vjay Kanabar        Sponsor               Professor,    Boston   Vjay.kanabar@bu.com
                                          University (BU)
Linda Reed          Project Manager       JDW Consulting          picardl@bu.edu
William Carron      Team Member           JDW Consulting          bcarron@bu.edu
Arjun Vyas          Team Member           JDW Consulting          arjunv@bu.edu
Aaron Wong          Team Member           JDW Consulting         awong@bu.edu
Joong Lee           Team Member           JDW Consulting         jblee@bu.edu
Donald Buresh       Advisor/Facilitator   BU representative      Donald.buresh@bu.com
Fred Santino        Advisor/Facilitator   BU representative      Fred.Santino@bu.com
Comments: The BU representatives will support the project as needed.



3   TEAM CONTRACT

Code of Conduct

       Work proactively, anticipate problems and work to prevent them
       Keep other team members informed of information related to the project
       Focus on what is best for the entire project team


    Participation
   Be honest and open during all project activities
   Encourage diversity in team work
   Provide the opportunity for equal participation
   Be open to new approaches and consider new ideas
   Have one discussion at a time
   Let the Project Manger Fred Santino know well in advance if a team member has to miss a meeting or may have trouble
    meeting a deadline for a given task.

Communication

   Decide as a team on the best way to communicate. We will use the team blog and WebCt and conference calls.
   We will invite the Facilitator Fred Santino and Prof Buresh on our weekly conference call.
   Work together to create the project schedule and enter this information into MS Project 2003 before the weekly meeting is held
    to determine what else needs to be done.
   Present ideas clearly and concisely
   Keep discussions on track and have one discussion at a time

Problem Solving

   We will encourage everyone to participate in solving problems. Let you team member know as soon as possible when a
    problem could delay the completion date.
   Only use constructive criticism and will focus on problem solving and not blaming people.
   Build off of each others ideas.

Meeting Guidelines

   We will meet every Tuesday evening at 7:00 PM Central time. The team will turn in each of their accomplishments to Linda
    Reed by Sunday 5:00 PM Central time of each week. The MS Project task schedule will be maintained and updated by
          William Carron. In addition, Linda Reed will develop the table of contents for the final project deliverable. Please send Linda
          Reed your documents when completed. I will keep the Final Project deliverable updated as information is submitted.

         Linda Reed will keep notes of the meeting minutes and send them out via email within 24 hours of the project status and any
          updates. Focusing on decisions made and action items for each meeting.

         Linda Reed develops an agenda before all meetings with discussion points submitted from each team member. Please submit
          your suggestions for discussion to Linda Reed no later than Sunday 5:00 PM central time of each week so the agenda can be
          updated and sent out. If there are no agenda items for discussion we can talk about the WBS to be sure we are within out
          timelines.

         Linda Reed will document major issues and decisions related to the project and send them out via WebCT to all team
          members, Fred Santino and Prof Buresh as needed.




  4   SCOPE STATEMENT

Project Title: Boston University Metropolitan College Web Project
Date: 17 June 2006            Prepared by: Team 2
Project Justification: Boston University Professor Vijay Kanabar requested this project for
CS632 to enhance the existing academic Project Management program and the existing annual
conference registration website, to showcase student and facility research and develop the
research page of the project management program at Metropolitan College. The web page
enhancements new functionality will create an automatic registration system for the annual
Project Management conference and store the information in the database on the web to allow
the conference chair to print the data dynamically. Another objective is to present on the web
selected research abstracts, podcast, videocast and PDF files of student research. The abstract,
podcast and videocast and PDF files will increase the students and facility visibility at Boston
University Metropolitan College. By showcasing the student’s and facility expertise prospective
students could be directed to the website to assist them in evaluating the educational value
received from Boston University Metropolitan College Project Management Program which
would increase student enrollment in the graduate degree program thus improving profitability.
The budget for the project is $1,000.00 with a $12.95 annual hosting fee. Estimated benefit of
the web project is $100,000 annually
Boston University Metropolitan College Web Project Characteristics and Requirements:

       1. Templates and tools: The web site will allow the conference chair an administrative
          login to print data dynamically, view the event calendar to manage, modify and add
          new events. The conference chair also has the capability to view reports by event,
          The website will also provide PDF files from student and facility research, podcast
          and videocast. In addition videocast and podcast conference papers.

       2. User submissions: Conference participants will be encouraged to register for the
          annual Project Management Conference thru the website. Students, facility and
          administration will have easier access to data.

       3. Articles: Facility and student research articles posted on the web site will have
          appropriate copyright permission. The format for the articles will be PDF, podcast
          and videocast.

       4. Requests for articles: The web site will include a section to showcase student and
          facility research.

       5. Links: All links to external sites will be tested on a weekly basis. Broken links will
          be fixed or removed within five working days of discovery.

       6. The “Nice to Have” feature such as the capability to videocast and podcast
          conference papers must be user-friendly and capable of soliciting questions and
          immediately acknowledging that the question has been received in the proper format.
          The feature must also be capable of forwarding the question to the appropriate expert
          (as maintained in the system’s expert database) and capable of providing the status of
          questions that are answered. The system must also allow for payment for advice, if
          appropriate.

      7. Security: The intranet site must provide several levels of security. All Boston
         University employees will have access to the entire intranet site when they enter their
         security information to access the main, corporate intranet. Part of the intranet will be
         available to the public for registration for the Program Management Conference the
         corporate Web site. Other portions of the intranet will be available to prospective
         students.
      8. Search feature: The intranet site must include a search feature for users to search by
         topic, key words, etc.

      9. The web site must be accessible using a standard Internet browser. Users must have
         appropriate application software to open several of the templates and tools.

      10. The web site must be available 24 hours a day, 7 days a week, with one hour per
          week for system maintenance and other periodic maintenance, as appropriate.

Summary of Web site Deliverables

Project management-related deliverables: Business case, Team contract, Scope statement,
Project Plan, Risk Management, Quality Standards & Quality Management Approach, Change
and Control Procedures and Project Notebook.

Product-related deliverables are Systems and Project Management documentation
   1. Business Case-
   2. Team Contract-
3. Scope Statement-

4. Project Plan:
Purpose, Background and Approach
Goals/objectives
Scope
Constraints
Assumptions
Related subprojects and critical dependencies

5. WBS
Determine Project Objective
Define Project Scope
Define Project Products
Determine Project Constraints
Select project approach
Assess initial phase project risks
Define the work breakdown structure
Define Project Milestones
Determine Project Organization
Estimate Top Down and Bottom Up Effort
Allocate Resources
Schedule Activities
Develop Budget for hosting
Refine Project Risk Assessment
Obtain Project Plan Approval
Milestones Schedule and milestones in MS project
Equip Project with Equipment and facilities
Identify training needs
Monitor Open Issues
Track Deliverables and Project Progress
Acknowledge Performance
Report Project Status to Instructor Weekly

6. Risk Management
Identification
Quantification
Mitigation
Contingency Plan

7. Quality Standards & Quality Management Approach
Functionality
System Outputs
Performance
Reliability
Quality Management
Quality Assurance Plan
Purpose
Policy Statement
Scope

8. Management
Organizational structure
Technical Mentor/Senor Management
Task Leader
Quality Assurance Team
Technical Staff

9. Change and Control Procedures
How changes and scope creep was managed

10. Project Notebook
   Roles and Responsibilities
   Team Blog
   Team Website
   Team Contact Directory
   Team Meetings
   Weekly Status Report
   Who does what and when (MS Project)

    11. End Project
    Prepare Completion Report
    Summarize Project Results
    Identify Lessons Learned
    Turn over Results
    Accept Project Results
    Review Resource Performance
    Perform Final Accounting
   Tools and techniques to be used
Project Success Criteria: Our goal is to complete this project within 22 days for no more than
$1,000.00 The project sponsor, Vijay Kanabar, has emphasized the importance of the project
completion by 21 June 2006. If the project submitted not later than Week 6 Prof Kanabar, Prof
Busresh and Fred Santino will still consider a B to A- range and if we exceed expectations for
functionality such as a private login for administration to see the conference participants, add a
shopping cart and include a good podcast and videocast of our project we will be given an A.




  5     PROJECT PLAN

  5.1   Purpose/Background/Approach
PURPOSE – BACKGROUND – APPROACH


PURPOSE/BACKGROUND: For the purpose of enhancing the annual project management conference and completing the objectives
for CS632, this project will automate the registration system for the annual project management conference by transforming the
current email driven registration system to a database driven system. This will help the conference chair to better and more efficiently
run the project management conference.

Approach: Group 2 will apply the waterfall methodology to develop the website and the project team will meet once a week to discuss
progress. All components of the project will be reviewed by all team members prior to turning in the project for final review.




5.2     Goals and Objectives

There are two main goals for this project:

      1) First is to create an automatic registration system for the annual Project Management Conference. Currently the Project
         Management Conference’s registration system is email driven. Information is gathered and sent by email during registration to
         the conference chair. This project sets out to transform the cumbersome email system to a database driven system. A database
         system would allow the conference chair to print the data dynamically as well as allowing the system to be more robust and to
         gain enhanced features. (Current Website: http://www.bu.edu/met/news/project_management/#)

      2) Second goal is to show case select research abstracts-podcasts-videocasts as well as publishing PDF files from students taking
         CS632 on the following website (http://www.bu-pm.com/cs632/research.htm)
      3) Related to the above project the goal is to finish the project in the given time frame (6/25/2006) as well as coming within the
         budget provided for this particular project ($1000). As well as accomplishing the stated objective of CS632 which are as
         follows.

               a. Gain practical knowledge of the major activities involved in project management and the ability to apply them in a real
                  software project
               b. Learn or enhance Web technology skills
               c. Work as part of the project team
               d. Gain the ability to divide tasks amongst the members and complete them on time and schedule
               e. Gain the ability to deal with stakeholders in geographically diverse locations
               f. Improve project management documentation skills
               g. Gain or enhance virtual presentation skills


      1.    Gather and meet team 2 for project kick off meeting by 2nd week
      2.    Define Team Lead (project manager) and project deliverables and assignments to team members 2nd week
      3.    Team meeting once a week
      4.    Develop initial website and test within team 5th week
      5.    Initial draft of project plan for review by team by 6/18
      6.    Review all project components for completeness before project due date
      7.    Turn in Project on time


5.3        Constraints/Assumptions

Assumptions:

           The scope of the Web project will not be larger than the time needed to complete the project which is approximately 4 weeks
      The schedule of the projects’ tasks will be completed before June 21st, 2006. The six members of team two will undertake their
       tasks assigned scheduled tasks, and report to the group regarding their progress.

      Financing for web hosting of the web project will be funded by the project sponsors.

      Resources for the project will come from within each team. Course instructors will be available for consult if the team decides
       additional resources are needed to complete the project

      Expectations that team members will participate in web project in accordance with team contract and prescribed roles.

      At least one member on the team will be familiar with the web development tools and technologies needed to develop and
       execute building of web project


Constraints:

      The timeframe for completing the entire project is 4 weeks. The period for completing the web project is between the kick off
       meeting and the priority deadline of deliverable determined by the team. The priority deadline for deliverable determined by
       the team is June 21st, 2006.

      Funding for the project will be limited by the University to support hosting for the website.

      Resources for the web project will mostly be self contained within the dynamics of the assigned group. Outside resources are
       limited after the group has been formed.

      Skill Levels for the project are limited to the pool of available students enrolled in course. Required skills for completion of the
       project are determined by the course professors.
5.4   Related subprojects/critical dependencies

Related sub projects for the web project involved setting up sub domains on www.ixwebhosting.com. In order for each group to
upload their project, each group needed a domain at the hosting web site. Setting up the hosting site was a complex process that
involved multiple group coordination and tasks that required planning and scheduling.
The setting up of the domains was critical for the display of the individual group projects. Without the web hosting project happening
first the group project could not be displayed.
5.5      Web Project WBS MS Project > Visio

                                                       METCS 632 Web Project
                                                               [0]




                                                                     Monitoring and
       Initiating [1]                 Executing [3]                                      Planning [2]         Closing [5]
                                                                     Controlling [4]


                        Print Registration     Quality Planning,     Create and Send      Create a
      Business Case                                                                                        Table of Contents
                        Form (By Event)        Testing and QA        Team 2 agenda     conference call
       Created [1.2]                                                                                             [5.2]
                              [3.12]           evidence [3.15]             [4.1]            [2.3]
                                                                                        Develop Team
      Team Contract      Manage Events          Print Report (By                                           Project Notebook
                                                                                            contact
       Ratified [1.7]        [3.10]              Event) [3.11]                                                   [5.1]
                                                                                       information [2.1]
  Develop Project                               DB schema, flow
                                                                                       Team Meeting
    Purpose and         Admin Menu [3.9]         chart and flow
                                                                                           [2.4]
  background [1.5]                               diagram [3.2]

      Project Charter     View Events                                                  Develop Project
                                                Admin Area [3.8]
       Signed [1.3]      Calendar [3.7]                                                 Scope [2.2]

  Develop Project
    Goals and             Design [3.4]         Include Files [3.5]
  Objectives [1.4]

  Project Manager                              Site map and user
                          Log Off [3.13]
  Determined [1.1]                               Manual [3.14]


       Write Team       Registration Form       Web Site design
      Contract [1.6]          [3.6]              complete [3.1]


                                                  Database
                                                Connection [3.3]
5.6   Schedule and Milestones (MS Project)




5.7   WBS (MS Project)


C:\Boston University\
CS632_project Management\CS632_Web Project_Team2\Team2_Web_Project.mpp



5.8   Tools and techniques

Html
Javascript
Asp
Allaire homesite
Frontpage
ms access


5.9       Budget for Hosting



          BU Development Budget $1,000.00

          Hosting Price for unlimited hosting: $12.95 per month

          Click on the URL to see site hosting features

http://www.ixwebhosting.com/index.php/home.dspPage/page/info.dspUnlimitedPro/IXWEBSESSION/ec859a295bb7d35423af94a20
c6228c4/IXWEBSESSION/ec859a295bb7d35423af94a20c6228c4



6     RISK MANAGEMENT


6.1       Risk Identification

Note: Risks are identified below as in a risk register with the number being a combination of Group 14 Team 2 and risks “a”
through “e”)

       No.: R142a
       Rank: 1
       Risk: Deliver an end product that is not what the customer wants
 Description: We have never done a job for this particular customer before. The project deliverables, while rather limited, allow
   for latitude in delivery.
 Category: People risk
 Root cause: Communication with customer
 Triggers: The project manager and project members are aware that this is our first project as a team and we could possibly
   misinterpret project requirements.
 Risk Response: Communicate with the project manager concerns about hitting the project expectations. Set up meetings with
   the project manager and ensure that our vision of the project matches the customers.
 Risk Owner: Team
 Probability: Medium
 Impact: High
 Status: Project lead has verified with the project manager the exact deliverables for this project.

   No.: R142b
   Rank: 2
   Risk: Not delivering a completed project
   Description: There is the possibility that one or more project expectations may not be completed.
   Category: People risk
   Root cause: Compressed time line with many deliverables
   Triggers: The team is aware that there is much to be done and the team leader has been diligent in maintaining deliverables
   Risk Response: The team clearly defined its perception of deliverables early on and made assignments to individual team
     members. Hard dates were given for item delivery and at each team meeting updates on deliverables were given. Extra effort
     was given to allow for team communication to include team blog, external email and phone conferences.
   Risk Owner: Team
   Probability: Medium
   Impact: High
   Status: The project has not yet been finalized but most deliverables and extras have been completed and are going through final
     review and assembly.
   No.: R142c
   Rank: 3
   Risk: Not having the technical skills to complete the project
   Description: Team members may not have the technical skills to complete all aspects of the project
   Category: People risk
   Root cause: Project that requires web development, database, MS Project skills
   Triggers: Project owner is aware of the skill need
   Risk Response: Team lead and members have taken every effort to assign tasks based off available skill sets
   Risk Owner: Team
   Probability: Low
   Impact: Medium
   Status: The team has divided up all deliverables to members with the expected skill set.


   No.: R142d
   Rank: 4
   Risk: Lack of communication within the team
   Description: Team communications may fail from time to time because the team is spread across the continent in different time
     zones with different daily schedules.
   Category: People risk
   Root cause: Geographic location variety
   Trigger: The team and project owner are aware that the team is spread out across America.
   Risk Response: The team has made every effort to create many levels of communication, to lay out an excellent work delivery
     schedule and to build in check points so that expectations are worked out in advance
   Risk Owner: Team
   Probability: High
   Impact: Low
   Status: Communication has been good throughout the life of this project thus far.
         No.: R142e
         Rank: 5
         Risk: Loss of a team member before delivery of project item
         Description: Two team members have indicated that they are being mobilized to active duty and perhaps being deployed. This
           activation is scheduled to occur during the project development stage. Other unforeseen developments may cause the loss of
           any other team member.
         Category: People risk
         Root cause: Military requirements or other requirements may cause a team member to miss on a project deliverable.
         Trigger: The team leader and team proper are aware of the possibility of member attrition
         Risk Response: The team has made efforts to be very open and honest about circumstances that may cause problems. Back-ups
           were discussed to cover the loss of a team member although nothing formal was set in place.
         Risk Owner: Team
         Probability: Medium
         Impact: Low
         Status: Member loss at this time has not had a negative impact on project deliverables.


6.2       Quantification
              Missed project above requirement deliverables causes a decrease in maximum grade available
              Missed project basic requirement deliverable causes a decrease in grade to below satisfactory level
              Team/sponsor communication problems can cause a project deliverable to be not what is expected and therefore decrease
                customer satisfaction
              Team communication problems can cause missed delivery of items which can lead to loss of project sponsor satisfactions
                and degradation in overall grade.


6.3       Mitigation
              Early, definite scope assignment
              Project communications, blogs, emails and conferences
          Deliverable assignment with set dates for review
          Project deliverable clarification


6.4   Contingency Plan
          Fall back to meeting absolute basic project requirements in the event that we are not able to deliver the above expectation
            requirements
          Hand off deliverables to team members who can do what is expected in the event that a team member is lost or cannot do
            what is expected
7   QUALITY, MANAGEMENT CHANGE AND CONTROL PROCEDURES




      Boston University Metropolitan College Web Project




        Quality Assurance and Quality Management Plan

                                          June 21, 2006
                                Team 2
Linda Reed, Arjun Vyas, William Carron,
 Patrick Dwyer, Joong Lee, Aaron Wong
7.1   Title Page

       Document Name:              Boston University Metropolitan College Web Project
                                   Quality Assurance and Quality Management Plan

       Publication Date:           June 2006

       Contract Number:            2006-146-001

       Project Number:             Task: 2006146001

       Prepared by:                Aaron Wong


       Approval:                   Dr. Vijay Kanabar, Boston University Metropolitan College
                                   Name and Organization


       Concurrence:                Linda Reed, JWD Consulting
       Name and Organization



This document was generated by the Boston University Metropolitan College Web Project team2. The Web project will be developed
for the Boston University CS 632/ IT Project Management Class.
Lifecycle Stage: Boston University Metropolitan College Web Project is in the Planning stage of the software lifecycle.

Approval: A completed stage exit will constitute approval of this document.

Document Owner: The primary contact for questions regarding this document is:

Aaron Wong, Quality Assurance / Quality Management writer
Boston University Metropolitan College Web Project Team2
Phone: (210) 568-9125
Internet: awong@bu.edu


7.2   Privacy Information

This document may contain information of a sensitive nature. This information should not be given to persons other than those who
are involved in the Boston University Metropolitan College Web Project or who will become involved during the lifecycle.


7.3   Introduction

This Quality Assurance and Quality Management Plan (QA/QMP) sets forth the process, methods, standards, and procedures that will
be used to perform the Quality Assurance and Quality Management function for the Boston University Metropolitan College Web
Project. The QA/QMP follows the Waterfall Methodology, modified to accommodate the project model adapted for the Boston
University Metropolitan College Web Project


7.4   Purpose
This QA/QMP provides a foundation for managing the Boston University Metropolitan College Web Project Quality Assurance and
Quality Management activities, and is based on project activities and work products as documented in the Boston University
Metropolitan College Web Project Plan. This plan:

     Identifies the QA/QM responsibilities of the project team and the QA/QM consultant.
     Defines Boston University Metropolitan College Web Project reviews and audits and how they will be conducted.
     Lists the activities, processes, and work products that the QA/QM consultant will review and audit.
     Identifies the QA/QM work products.
     When independent assessments and project reviews such as in-stage assessments (ISAs) and stage exits, will be conducted and by
      whom.
     Applicability of published standards and procedures.
     Monitoring for adherence to applicable standards and procedures.
     Resolution of discrepancies.
     Assessment of project progress.
     Assuring the integrity of the software product.


7.5     Scope

Boston University Professor Vijay Kanabar requested this project for CS632 to enhance the existing academic Project Management
program and the existing annual conference registration website, to showcase student and facility research and develop the research
page of the project management program at Metropolitan College. The web page enhancements new functionality will create an
automatic registration system for the annual Project Management conference and store the information in the database on the web to
allow the conference chair to print the data dynamically. Another objective is to present on the web selected research abstracts,
podcast, videocast and PDF files of student research. The abstract, podcast and videocast and PDF files will increase the students and
facility visibility at Boston University Metropolitan College. By showcasing the student’s and facility expertise prospective students
could be directed to the website to assist them in evaluating the educational value received from Boston University Metropolitan
College Project Management Program which would increase student enrollment in the graduate degree program thus improving
profitability. The budget for the project is $1,000.00. Estimated benefits are $100,000 annually.
7.6       Background

This new Web site will provide visitors with the opportunity to register for the Annual Project Management Conference.

          Enhance the existing academic program in project management website and the existing annual conference registration
           website.
          The website will showcase student and faculty research.
          Other specifications will be provided as you build the website. For example a “Nice to have feature” is to videocast and
           podcast your conference papers.

Boston University Metropolitan College are interested in the following features
      Automated Registration
      Administrator’s Page which has to be password protected. That will allow us to see the conference registrations and print the
       data.
      Create research page classified by topics. Showcase sample research papers or podcasts.


7.7       Project Checkpoints

Each stage of development will have at least one formal checkpoint called a stage exit. When a stage has been successfully exited, it
indicates that all draft deliverables due to date have been completed, all outstanding issues have acceptable action plans, and there is a
sound plan for the remainder of the project (detailed for the next stage). The project's designated approvers (sign-off authorities) must
provide a written position of concur/non-concur at stage exit. All affected functional areas involved in the project also participate in
and can provide input to the stage exit
7.8   QA/QM Roles and Responsibilities


The following chart defines the QA/QM roles and responsibilities of the members of the project team and their function at stage exit.

       Note: Due to staffing fluctuations, if a particular person is unable to fulfill his/her responsibilities, it will be the responsibility
       of the manager overseeing that area to ensure a replacement, with appropriate skills and experience, on a timely basis.


                                                                                                           Stage Exit
                    Role            Name               Org.          QA/QM Responsibility                  Function
                                                       JWD
                    QA              Aaron Wong                       Manages the Quality Assurance         Approve
                                                       consultin
                    Manager                                          function.                             (delegated
                                                       g
                                                                                                           to QA
                                                                                                           consultant)
                    System          Dr. Vijay          Boston        Helps define product quality          Approve
                    Owner           Kanabar            University    expectations. Represents
                                                                     procurement users. Determines
                                                                     final acceptance of BUMC Web
                                                                     Project.
                    QA              Joong Lee          JWD           Audits and approves project           Approve
                    Consultant                         consultin     deliverables from QA
                                                       g             perspective. Reviews plans and
                                                                     deliverables for compliance with
                                                                     applicable standards. Provides
                                                                     guidance and assistance on
                                                                     process matters.
                                                                                                        Stage Exit
                    Role           Name               Org.         QA/QM Responsibility                 Function
                    Project        Linda Reed         JWD          Ensures implementation of            Conduct
                    Manager                           consultin    quality activities. Coordinates
                                                      g            resolution of issues. Provides
                                                                   regular and timely
                                                                   communications.
                    Project        Fred Santino       Boston       Monitors implementation of           Approve
                    Manager's                         University   quality activities. Receives
                    manager                                        reports on BUMC Web Project
                                                                   quality efforts. Resolves conflict
                                                                   across organizations.


The role of the Boston University Metropolitan College Web Project QA team is to assist the technical staff to continually improve the
quality of their work products and services. The QA team is responsible for establishing processes and procedures that accurately
verify and validate the adherence of desktop computer support, Help Desk and network activities to applicable standards, guidelines,
and procedures.

The Boston University Metropolitan College Web Project QA team will be involved at the start of the project. They will participate in
the development of the Boston University Metropolitan College Web Project Management Plan (PMP), also the Phase I Transition
Plan to establish their function within the project and to provide input into the project’s schedule and work breakdown structure
(WBS). To ensure that QA activities are identified and that time is allotted for QA activities. Funding for the QA team members will
be planned within the task hours and cost structure.

The organizational responsibilities as they relate to QA are:
7.9   Senior Management

                Provides management support, supervision, and oversight for the QA function
                Ensures the independence of the QA function
                Makes available staff and other resources as needed to support QA
                Ensures resolution of problem and concern issues
                Reviews QA audits and reports


7.10 Web Project Task Leader

                Manages overall Boston University Metropolitan College Web Project performance.
                Ensures QA activities are conducted
                Ensures compliance with the QA program
                Ensures responses to deficiency reports from QA reviews and audits


7.11 Quality Assurance Team

                Develops and maintains the Quality Assurance Plan
                Conducts audits and reviews
                Ensures work products adhere to the appropriate standard
                Develops audit and review procedures for YYYY activities
                Ensures the QA processes and procedures adequately control project quality
                Ensures the QA activities accurately measure the product, service and process quality
                Reviews and approves specified deliverables for release to customer
                Promptly reports results of audits to the project task leader
                Periodically reports unresolved noncompliant items to technical monitor/senior management
                Maintains an on-going dialogue with the technical monitor and Boston University Metropolitan College Web
                 Project support staff
                  Ensures that the expectations of QA activities are identified and understood between the
                  technical monitor, task leader, and the team members
                  Collects and analyzes metrics produced from the results of the QA process
                  Recommends changes in procedures to improve processes


7.12 Technical Staff

                  Implements task level quality control based on QA standards, policies, and procedures
                  Participates in reviews and audits
                  Performs corrective actions or process improvements in response to QA findings
                  Manages and controls defects/errors and corrections
                  Tracks the status of defects/errors until closed

The effectiveness of the QA team’s effort depends on the support and commitment of the technical staff and all levels of management.
All affected groups should be trained in the principles of quality assurance and be committed to the proper inclusion and performance
of QA activities within their work efforts.



7.13 Required Skills

The Quality Assurance consultant must be able to review iterations of the Project Plan and lifecycle work products to determine
adherence to industry standards, as modified and documented in the Project Plan, and provide expert assistance on project
management practices and software development process related matters.

This position will ensure objective audits of the work products as they are being developed and objective reviews of project
management processes and stage exits.
7.14 Quality Assurance Procedure


Different methods and techniques will be utilized depending on the specific quality assurance activity. The techniques, tools, and
procedures that will be used are as follows:

          Walkthroughs - Formal or informal, structured walkthroughs are used for orientation, examining promising ideas,
           identifying defects or errors, and improving products at any stage in the process.
          Reviews - An independent evaluation of an activity or process to assess compliance with the project plan; or to examine
           products or processes against quality factors through the use of checklists, interviews, and meetings.
          Audits - An independent examination of a work product or process to determine compliance with specifications, standards,
           contractual agreements, or other pre-established criteria.
          Evaluations - An evaluation activity that examines products/services to determine compliance to customer requirements.
          Process Improvement - A process improvement program designed to reduce the error rate in a process.

Boston University Metropolitan College Web Project Quality Assurance will provide an independent review of the processes used at
key check points. These reviews will seek to identify risks early, and will simplify monitoring and managing problem areas
throughout the project. Due to the dynamic nature of Boston University Metropolitan College Web Project activities and the need to
provide quick response requests, the QA team and the technical monitor will identify the sign-off points at key check points of an
activity to ensure that expressed goals and requirements are met.


7.15 Walk Through Procedures

Walkthroughs are beneficial for evaluating plans, documentation and other deliverables and serve to orient staff members to new
technology products and services. Walkthroughs will be conducted internally and on an as-needed basis. They will be used to:

          Present plans, documentation, or other deliverables for review and approval.
          Review material in the preparation stages.
          Critique and report quality deficiencies of plans, processes, and procedures.
Walkthroughs will be scheduled early enough to allow for revisions if problems are identified. Records of these walkthroughs will be
maintained, along with issues that were identified and resulting action to be taken. Issues can be accepted “as is” or may require more
work. If further discussion on the issue is required, additional walkthroughs can be scheduled.


7.16 Review Standards

The Boston University Metropolitan Web Project Plan will follow the Waterfall Methodology standard. All lifecycle work product
standards are documented in the Boston University Metropolitan Web Project Plan. They include the following:

   ANSI/IEEE Guide to Software Requirements Specifications
   IEEE Guide to Software Design Descriptions
   IEEE Standard for Software User Documentation



7.17 In stage Assessments

Quality Assurance for this project will include at least one audit of all current draft deliverables and selected work products in each
stage of development. The reviews will assure that the established system development and project management processes and
procedures are being followed effectively, and exposures and risks to the current Project Plan are identified and addressed.

An in-stage review is an In-Stage Assessment (ISA), performed and documented by the Boston University Metropolitan Web Project
Quality Assurance consultant, in accordance with the In-Stage Assessment Process Guide.

The following diagram depicts the In-Stage Assessment process flow for all Boston University Metropolitan Web Project
development stages:


                                                      In-Stage Assessment Process
       PLANNING    │                 │   Stage exit milestones
       STAGE       │ PLAN PROJECT's │    defined in the QA/QMP for
                   │ STAGE EXITS     │   each stage
                   │                 │
                   └─────────────────┘

                   ┌─────────────────┐
        ALL        │    SCHEDULE     │   Schedule exit for the
       STAGES      │     CURRENT     │   current stage; notify
                   │      EXIT       │   participants (memo)
          │        │                 │
          │        └────────┬────────┘

          │        ┌─────────────────┐
          │        │   DISTRIBUTE    │   Distribute current proj.
          │        │    CURRENT      │   plan and other items
          │        │     PROJECT     │   needed to evaluate stage
          │        │       PLAN      │
          │        └────────┬────────┘

          │        ┌─────────────────┐
          │        │                 │   Receive positions and
          │        │     RECEIVE     │   qualifications (if any)
          │        │    POSITIONS    │   from participants
          │        │                 │
          │        └────────┬────────┘

          │        ┌─────────────────┐
          │        │                 │   Prepare plans to resolve
          │        │     PREPARE     │   qualifications (if any
          │        │ ACTION PLANS    │   were raised)
          │        │                 │
          │        └────────┬────────┘

          │        ┌─────────────────┐
          │        │                 │   Present plans addressing
          │        │     CONDUCT     │   qualifications and
          │        │ CLOSURE MEETING │   secure concurrence
          │        │                 │
          │        └─────────────────┘
          │



Each deliverable will be reviewed to make judgments as to the quality and validity of the deliverable or work product. The assessment will
include any verification or validation activities.
An issue will be documented and discussed in the team meeting for resolution. Once a list of issues has been compiled, it will be reviewed
with the project manager to see if any new or additional information might mitigate or eliminate any of them. Remaining issues must be
addressed with an action plan from the project manager. Issues from an In-Stage Assessment near the end of a stage might become
"qualifications" to the current stage exit.

An assessment of risk to the schedule for both the next stage and the remainder of the project, from the ISA reviewer's (QA
consultant) perspective, will also be provided. Risk categories are as follows:


        Low                Potential or existing problems must be addressed to avoid an impact to the current Project Plan. This would also
                           apply if no issues were identified.

        Medium             Problems exist that have a high probability of impacting the current Project Plan or other dependencies.

        High Serious problems exist (without an acceptable plan to resolve) that have a high probability of impacting user
                    acceptance, the current Project Plan, or other dependencies

In-Stage Assessment Report

Project Name__________________________________________________________________

Stage of development                                 Date_______________________

Reviewer                                         Phone________________________



No.     Issues/Concerns:                                                Resolved

        _________________________________________________________ ________

        _________________________________________________________ ________
       _________________________________________________________ ________

       _________________________________________________________ ________

       _________________________________________________________ ________

       _________________________________________________________ ________

       _________________________________________________________ ________

       _________________________________________________________ ________

       _________________________________________________________ ________

       _________________________________________________________ ________


Assessment of risk to schedule

Low           Medium                 High

G              G                     H      For the next stage

G              G                     G      For the remainder of the project

A Stage Exit is the vehicle for securing the concurrence (i.e., approval) of designated individuals to continue with the project and
move forward into the next stage of development. The concurrence is an approval (sign-off) of all draft deliverables, including the
Project Plan, and selected stage work products produced to date. The deliverables and work products (if any) are assured via the In-
Stage Assessment process described previously. The Stage Exit indicates that all qualifications (issues and concerns) have been
closed or have an acceptable plan for resolution.
7.18 Stage Exits

The purpose of a Stage Exit is to:

   Allow all functional areas involved with the project to review the current Project Plan. This includes, at a minimum, a detailed
    plan for the next stage, and high-level plans for the remainder of the project.

   Provide a forum to raise qualifications (issues and concerns) if issues exist that will impact the Project Plan.

   Ensure an acceptable action plan exists for all qualifications raised.

   Obtain concurrence on current stage draft deliverables, and to begin the next stage of development.

With any software development/integration project, lifecycle stages may overlap as activities of the new stage are beginning and
activities of the previous stage are completing.

The Stage Exit process begins with a notification to the extended development team that a stage exit has been scheduled. The process
ends with the receipt of concurrence from the designated approvers to proceed to the next stage. Concurrence indicates that all known
issues have an acceptable plan for resolution.

The following are the minimum inputs to the Stage Exit process:

   System development lifecycle deliverable(s)
   Current project plan
   Issues to be addressed (generic)
   Concurrence/qualifications from the approvers
   Issues that remain open from the last In-Stage Assessment

The following diagram depicts the Stage Exit process flow:

                       ┌─────────────────┐
PLANNING   │                   Stage exit milestones
STAGE      │ PLAN Project’s    defined in the QA/QMP for
           │ STAGE EXITS     │ each stage
           │
           └─────────────────┘

           ┌─────────────────┐
 ALL       │    SCHEDULE     │ Schedule exit for the
STAGES     │     CURRENT     │ current stage; notify
           │      EXIT       │ participants (memo)
   │
   │       └────────┬────────┘
   │
   │       ┌─────────────────┐
   │         DISTRIBUTE        Distribute current proj.
   │          CURRENT          plan and other items
   │           PROJECT         needed to evaluate stage
   │             PLAN
   │       └────────┬────────┘
   │
   │       ┌─────────────────┐
   │                             Receive positions and
   │           RECEIVE           qualifications (if any)
   │          POSITIONS          from participants
   │
   │       └────────┬────────┘
   │
   │       ┌─────────────────┐
   │       │                 │ Prepare plans to resolve
   │       │     PREPARE     │ qualifications (if any
   │       │ ACTION PLANS    │ were raised)
   │       │                 │
   │       └────────┬────────┘
   │
   │       ┌─────────────────┐
   │       │                 │    Present plans addressing
   │       │     CONDUCT     │    qualifications and
   │       │ CLOSURE MEETING │    secure concurrence
              │            │                 │
              │            └─────────────────┘


Each approver will respond to the Boston University Metropolitan College Web Project Manager using the Stage Exit Position
Response form shown on the next page.


Stage Exit Position Response Form


Project name: Boston University Metropolitan College Web Project

Project stage:__________________________________________

Return form to:        Linda Reed, Project Manager

Return by:    ____________________________________________


Position: _____________________________________________

G Concur - Proceed with the project according to the current Project Plan.

G Concur with qualifications - Issue(s) exists. The project can proceed according to the current Project Plan if there is an acceptable action plan for each issue by
the stage exit meeting.

G Non-concur. - Significant issue(s) exist. The project should not proceed to the next stage until the issue(s) is resolved.


Qualifications (issues):
Approver: ______________________________________
           (please print)

Signed:                                            Date: __________________
7.19 Peer Review

A minimum of one peer review will be performed on each deliverable.


7.20 Audit Process

The QA team is responsible for conducting product/service and process audits. The purpose of audits is to identify deviations in
process performance, identify noncompliance items that cannot be resolved at the technical support or project management level, to
validate process improvement/corrective action achievements, and to provide relevant reports to all management levels.

A product audit is an independent examination of work product(s) to assess compliance with specifications, standards, customer
requirements, or other criteria. Product audits are used to verify that the product was evaluated before it was delivered to the
customer, that it was evaluated against applicable standards, procedures, or other requirements, that deviations are identified,
documented, and tracked to closure and to verify corrections. A process audit is a systematic and independent examination, to
determine whether quality activities and related results comply with planned arrangements. And whether these arrangements are
implemented effectively and are suitable to achieve Boston University Metropolitan College objectives

The QA team will perform the following activities when conducting an audit:

                 Define the scope and purpose of the audit within the audit plan.
                 Prepare audit procedures and checklists for the audit.
                 Examine evidence of implementation and controls.
                 Interview personnel to learn the status and functions of the processes and the status of the products.
                 Discuss findings with the technical staff and task leader.
                 Prepare and submit an audit report to technical monitor/senior management
                 Refer unresolved deviations to technical monitor/senior management for resolution.
7.21 Audit Procedure


A typical audit would include the following steps

   1.      Clearly understand and adhere to the audit scope
   2.      Conduct preparation meetings in advance of the audit.
           a. Define areas to be reviewed.
           b. Define review criteria.
   3.       Conduct an overview meeting in advance of the audit
   4.      Understanding of Web Project organization, products, and processes.
   5.      Conduct the planned meetings, interviews, samples, etc.
   6.      Review the preliminary findings internally with the audit team.
   7.      Verify and classify findings from the audit.
   8.      Validate audit findings with the audit recipient.
   9.      Prepare the audit report for the audit client.
   10.     Provide recommendations on request only.
   11.     Follow-up on corrective action/process improvement.
   12.     Improve the audit process.

An audit is considered complete when

                 Each element within the scope of the audit has been examined.
                 Findings have been presented to the audited organization.
                 Response to draft findings have been received and evaluated.
                  Final findings have been formally presented to the audited organization and initiating entity.
                  The audit report has been prepared and submitted to recipients designated in the audit plan.
                  Document audit findings and recommendations and report to Project Manager.
                  The recommendation report, if required by the plan, has been prepared and submitted to recipients designated in the
                   audit plan.
                  All of the auditing organization's follow-up actions included in the scope of the audit have been performed.




7.22 Evaluation Process

Evaluations examine the activities used to develop/deliver products and services, ultimately determining if the activity is fulfilling
requirements. The QA function establishes criteria for an evaluation, verifies the process has been performed, and collects the metrics
to describe the actual results of those activities.



7.23 Process Improvement


The QA team is responsible for process improvement. Process improvement is successful when an effective process emerges or
evolves that can be characterized as: practiced, documented, enforced, trained, measured, and improvable.

A corrective action plan must be developed when a deficiency in the process is detected. Corrective action should prevent the problem
from recurring.
 Successive steps for implementing a process improvement approach are:

   1. Detection of quality-related problems
   2. Identification of responsibility
   3. Evaluation of importance
   4. Investigation of possible causes
   5. Analysis of problem
   6. Preventive action
   7. Process controls
   8. Disposition of nonconforming items
   9. Permanent changes

The QA team will analyze the results of their findings in relation to the results of documented processes used to produce products or
services. This comparison will be used to determine which process may need improvement and to determine the effectiveness of
changes to the processes. This comparison will also be used to identify best practices that should be continued or implemented at
other sites


7.24 Problem Reporting Procedures

Errors, defects, issues, deviations and noncompliance items identified in the Boston University Metropolitan College Web Project
activities must be itemized, documented, tracked to closure, and reported by the QA team. The QA team must verify all problems
were tracked to closure and must provide continuing feedback to management and the technical support team concerning the status of
the problem.


7.25 Non Compliance Procedures

                  Problems are resolved with the task leader, when possible.
                   Problems that cannot be resolved with the technical team or task leader are elevated to Fred Santino.
                   Problems that have been referred to the project manager are reviewed weekly until they are resolved. Items that
                    cannot be resolved by the project manager within six weeks are elevated to the Fred Santino for resolution.

7.26 Quality Assurance Management Plan


Yes    No       Check List Description
_x__   ___      Are project tracking activities evident?
_x__   ___      Are project tracking and oversight being conducted?
_x__   ___      Are all plan reviews conducted according to plan?
_x__   ___      Are all issues arising from peer reviews addressed and closed?
_x_    ___      Are status and review meetings conducted according to the schedule?
_x__   ___      Is a WBS that supports all deliverables/long term projects developed?
_x__   ___      Is change managed according to the Configuration Management Plan?
___    _N/A__   Have all deviations from standards and procedures documentation been approved?
_x__   ___      Are project roles and responsibilities defined


7.27 References

   ANSI/IEEE Standard for Software Verification and Validation Plans
   Software Engineering Institute, QA/QM Key Process Area
   Information Technology Project Management, fourth edition, 2006
8     HOW OUR TEAM MANAGED CHANGES AND SCOPE CREEP
The goal in managing scope creep for Team 2 was to minimize the impact of any changes
on the project, such as the feature requirements and timelines. Within the second team
meeting we had all reviewed and agreed upon the feature options of the web project and
made a commitment to meet the project deadline as agreed upon. When an issue came up
such as how to create individual podcasts within the Team Blog a decision was made as
to how to resolve this issue and we agreed upon by all. Any modifications by Prof
Kanabar and Fred Santino were discussed in our weekly team meetings so that all
members were aware of the changes and possible impact on the project. The changes
were agreed upon by all team members consciously and were given the opportunity to
voice approval or disproval with everyone being aware of the consequences of the
changes, such as an increase in the project timeline. As the team proceeded through the
various phases of our project we never lost site of our goal. The requirements may have
not been well defined or understood up front but we were able to keep in touch with Prof
Kanabar, Fred Santino and Prof Buresh and communicate our concerns. The key factor in
minimizing scope creep for our team was to anticipate potential problems and manage
them as the web project progressed.




9     PROJECT NOTEBOOK

9.1   Roles and Responsibilities
Sequence      Initials    Responsibility                     Start Date End Date
Number
1             WC          Content Team WBS, Schedule and 6-Jun-06       21-Jun-06
                          Milestones, Editor, Copywriter
2             PD          Content Team Risk Management,  6-Jun-06       21-Jun-06
                          Quantification, Mitigation,
                          Contingency Plan, Editor and
                          Copywriter
3             AV          Information Architect Developer,   6-Jun-06   21-Jun-06
                          Designer, Production Artist,
                          Technical Lead
4             JL          Content Team, Scope Statement,     6-Jun-06   21-Jun-06
                          Project Plan Development, Editor
                          and Copywriter
5             AW          Content Team Quality Standards     6-Jun-06   21-Jun-06
                          and Quality Management, Editor
                          and Copywriter
6             LR          Team Leader, Project Notebook,     6-Jun-06   21-Jun-06
                          Final Project Report




50
                   9.2    Team Blog
                   http://cs632team.blogspot.com/


                   9.3    Team 2 Website
                   http://cs632s14t2.bu-pm.com/

                   9.4    Team Contact Directory
Name                     Email1                 Email2                          Cell Phone     Work Phone     Home phone
Aaron Wong               awong@bu.edu           aaronhw@yahoo.com               N/A            210-977-3457   210-568-9125
Arjun Vyas               arjunv@bu.edu          arjunvyas@comcast.net           781-632-3927   978-774-0774   781-715-1214
Donald L. Buresh         thru webct             N/A                             N/A            N/A            847-872-1659
Fred Santino             thru webct             N/A                             N/A            781-377-9003   N/A
Joong Lee                jblee@bu.edu            jblee@att.com                  770-363-5031   770-750-3990   N/A
Linda Reed               lreed@bu.edu           N/A                             618-792-1606   N/A            618-239-9069
Patrick Dwyer            patrick.dwyer@hp.com   patrickdwyer@coronadofamily.c   619-204-7756   858-655-7455   619-522-0498
                                                om
Prof Kanabar             thru webct             N/A                             N/A            N/A            N/A
William Carron           bcarron@bu.edu         bicarron@gmail.com              N/A            N/A            617-653-7122




                   10 TEAM MEETINGS

                   10.1 Week 3 Kick-Off Meeting

                   Team2 CS632
                   Conference Call Tuesday 30 May 2006 7:00 PM Central Time. 47 minutes duration

                   Team 2 Members (6 member team)
                   William Carron, Patrick Dwyer, Arjun Vyas, Joong Lee, Aaron Wong and Linda Reed

                   RE: Kick off Meeting

                   Team Members in attendance on Monday 30, 2006 at 7:00 PM Central time.
                   1. William Carron
                   2. Arjun Vyas
                   3. Joong Lee
                   4. Linda Reed

                   Team Members not in attendance 30 May 2006 at 7:00 PM Central time
                   1. Patrick Dwyer
                   2. Aaron Wong

                   In addition to the information listed below it was agree upon by the team members in
                   attendance that any and all email and other communications will be sent to the entire



                   51
team. The information may or may not apply to everyone but we will all be kept in the
loop. ** Please note if the email sent is to a specific to a team member that requires a
response from him or her.

It was also discussed and agreed upon that our team would use WebCT for our ongoing
emails and communication. By doing so it would keep the information in one place and
attachments could be reviewed by all. Once you have completed a task please send it to
the team for review and approval and remember to send an email if you accept the
document as is and have no request or suggestions for change. Once the item has been
approved by the Team Linda Reed will update the Final Project Table on contents.

The Team agenda meeting notes will be reviewed and agreed upon by all team members
before Linda Reed submits our weekly status to Fred Santino. No email response from
team members expresses acceptance of the minutes. Please check your email daily so we
can expedite completed work and keep our Web project on schedule.


Agenda Items:

       Appoint Team Leader. Team Leader will Report to Fred Santino with weekly
        status reports from the team.(20% of grade for Project Management)
     Team Leader appointed Linda Reed

        Comments and or Revisions of Team Contract or acceptance

     The Team Contract will be reviewed by each team member. Linda Reed will
     send out an email requesting each team member acceptance. Recommendations
     for changes will be implemented as needed.

         Discuss Features and Functions and who has the expertise to complete these
         tasks.
     Arjun will submit a list of High Level Features and create a task list for the web
     development with duration time. Expected completion dates. Our goal is to
     complete the Web project by 21 June 2006. In our team kickoff meeting
     discussion it was mentioned that Aaron Wong is an oracle Developer and could
     possible assist with this effort. It was agreed with would create the actual
     requirements for creating the website and would strive to exceed the expectation
     examples.
                Features and Functions

               To get a B to A- range

                    The team will provide a fully functional web system that does Web
                     based conference registration
                    Provide a like to your team members 2 page paper/podcast from
                     the research.htm page.



52
                To get an A you must EXCEED expectations examples:

                     Private login for admin to see conference participants
                     Shopping cart
                     Good podcast and Video cast of your article

        Discuss and review the SCOPE Statement determine revisions if any or
         acceptance. (Joong Lee is revising the scope statement)

        Assign tasks per the SCOPE statement (See the WBS information below to be
         completed in MS Project by Bill Carron

Assign deliverables for the final Web Project (80%)
If you are assigned to a deliverable please determine the duration needed and any
constraints to input into MS Project to include an expected completion date. Add
any additional assumptions.

      Business Case (see page 82-85 of Schwalbe text)
     Assigned to Bill Carron
      Team Contract (completed by L Reed 30 May 06 and request acceptance at team
        meeting. Revisions discussed per the team will be implemented )

The team contract will be reviewed by each team member. Any team member
requesting additions to this document and or suggestions for revision should
document them in another color and send it out to all Team Members

        Scope Statement (Linda Reed’s Week 2 Scope statement sent to team for review
         and suggestions for changes) the revised SCOPE statement based off of team
         input could be submitted as the deliverable.

Joong Lee will make revision to the scope statement in another color so we can all
view what has been changed and submit it to the team for acceptance.

        Project Plan to include:

     AV will send the MS project template to the team for the Project Plan. (This was
     sent to the Team on 30 May 2006 during the Team Meeting. (Thanks Arjun)

          Purpose/Background and approach
          Goals and Objectives
          Scope (see above)
         The above items highlighted in yellow have been assigned to Joong Lee




53
         Deliverables Assigned to Linda Reed (Note: Linda Reed sent an email to
          Prof Kanabar on Tues 30 May 2006 requesting confirmation of all
          deliverables.

          Constraints/assumptions
          Related Sub projects/critical dependencies
          WBS (see scope statement information includes Appendix A suggested tasks)
          Schedule and milestones (MS Project)
          Tools and techniques to be uses
                   Technical
                   Non technical
        The above items have been assigned to Bill Carron



Budget for hosting: Hosting information submitted to team by Vijay Kanabar on Sunday
29 May 06. Hosting with IX Web Hosting (grading rubic 40% for a functioning
website) Assigned to Arjun
Note: (Arjun has sent an email to Prof Kanabar on 30 May 2006 to clarify what
Arjun needs to know for hosting the website.


Risk Management
       Identification, quantification, mitigation, contingency plan
As of 30 May 2006 kick off meeting this task was not assigned. It was agreed this
task would be discussed at a later date. (It’s possible that Patrick Dwyer or Aaron
Wong can assume this task but that has not been resolved.)

Quality Standards & Quality Management approach. Email 1 June 2006 from Aaron
Wong accepted this task.

Project Notebook
    Roles and Responsibilities
        (Linda will create this)

        Team Blog
      (Team blog already created by Arjun)

         Team contact, directory, team meetings
        (Linda will document all team members and their contact information.)
        (Linda will find out what is meant by the term directory for the project
        notebook, and find out if the weekly agenda is updated and the content
        approved by each team member will suffice for the team meeting
        information.




54
          Weekly status report (Linda will submit a weekly status report to Fred Santino
            the following day of our Team Meetings
         Those in attendance on 30 May 2006 have agreed that Tuesday evenings at
         7:00 PM Central time is good for everyone.

          Who does what, when (MS Project gives this report)
         Bill Carron will take care of this.


        Final Report Project Table of Contents (page 108 of Schwalbe text)
         Linda Reed was assigned this task.


10.2 Week 4 Team Meeting
Team2 CS632
Conference Call Tuesday 6 June 2006 7:00 PM Central Time 50 minutes duration

RE: Week 4

All team members were in attendance for the conference call Tuesday 6 June 2006
7:00 PM Central Time.


Team Members:
1. William Carron
2. Arjun Vyas
3. Joong Lee
4. Linda Reed
5. Patrick Dwyer
6. Aaron Wong

Once the item has been approved by the Team Linda Reed will update the Final Project
Table on contents. “How do we want to handle the approval process for the
deliverables? 6 June 06 –All team members will send the document via email and
ask for approval. If you have suggestions for changes please send those
recommendations back to the person in charge of the deliverable and /or let them
know what they have is OK. If no response that means you are in agreement.

Reminder: To approve deliverables: Please check your email daily so we can
expedite completed work and keep our Web project on schedule.
 6-6-06 Everyone confirmed

Agenda Items:


        Comments and or Revisions of Team Contract or acceptance


55
     The Team Contract will be reviewed by each team member. Linda Reed will
     send out an email requesting each team member acceptance. Recommendations
     for changes will be implemented as needed. (Agree that this document was
     accepted by all. Linda will add the Team Contract to the Table of contents.
     6-6-06 Done ready for table of contents.


        Discuss Features and Functions and who has the expertise to complete these
        tasks.
     Arjun will submit a list of High Level Features and create a task list for the web
     development with duration time. Expected completion dates. (Has the list been
     revised with the final features and functions?

6 June 2006 Arjun has discussed and has finalized the requirements. Arjun will
send out the final web features and a task list so Bill can update the MS project
WBS for Arjun’s web development piece.

     Our goal is to complete the Web project by 21 June 2006. Are we still on track
     for 21 June completion? Arjun, do you need any help from Aaron? 6 June 2006
     No, Arjun will complete the task.

     It was agreed with would create the actual requirements for creating the website
     and would strive to exceed the expectation examples. From the email Arjun sent
     out I thought the features he suggested are within the exceed level do we all
     agree? 6 June 2006 Everyone agree and confirmed that Arjun’s feature list
     meets our expectations for exceed and will move forward with the features that
     Arjun recommends.

        Discuss and review the SCOPE Statement determine revisions if any or
         acceptance. (Joong Lee is revising the scope statement) Joong how are the
         revisions on the scope statement coming along? 6 June 2006 Joong’s expected
         completion date will be 21 June 2006

        Assign tasks per the SCOPE statement (See the WBS information below to be
         completed in MS Project by Bill Carron Bill, how is the WBS coming along
         in MS project? Has the file been created? Do you need any information from
         us to update it? 6- June 2006 Arjun will send the planning development and
         stages of the web pages, etc. to Bill along with how much time it takes for
         each task. Example in 30 minute time increments. Linda will do the same for
         the project management piece. Example: How long does it take to initate
         conference calls, etc. Bill would like this information from Linda and Arjun
         by our next weeks meeting of Tues 13 June 2006. Also the team is to send to
         Bill how long it takes to complete their deliverable so all this information is
         adequately documented too.




56
Assign deliverables for the final Web Project (80%)
If you are assigned to a deliverable please determine the duration needed and any
constraints to input into MS Project to include an expected completion date. Add
any additional assumptions.

      Business Case (see page 82-85 of Schwalbe text)
     Assigned to Bill Carron Bill, how is the business case deliverable coming along,
     do you need any help with it? 6 June 2006 Bill ECD (expected completion date is
     21 June 2006


Deliverables:

     Scope Statement: Joong Lee? 6 June 2006 Joong ECD (expected completion date
     is 21 June 2006


        Project Plan to include:


          Purpose/Background and approach
          Goals and Objectives
          Scope (see above)
         The above items have been assigned to Joong Lee.
     Joong do you need any help with these item for the project plan? Are you on
     track for 21 June? 6 June 2006 Joong ECD (expected completion date is 21 June
     2006



           Constraints/assumptions
           Related Sub projects/critical dependencies
           WBS (see scope statement information includes Appendix A suggested tasks)
           Schedule and milestones (MS Project)
           Tools and techniques to be uses
                    Technical
                    Non technical
        The above items have been assigned to Bill Carron
        Bill do you need any help with these item for the project plan? Are you on
        track for 21 June?
     6 June 2006 Bill ECD (expected completion date is 21 June 2006


Budget for hosting: Hosting information submitted to team by Vijay Kanabar on Sunday
29 May 06. Hosting with IX Web Hosting (grading rubic 40% for a functioning
website) Assigned to Arjun


57
Note: (Arjun has sent an email to Prof Kanabar on 30 May 2006 to clarify what
Arjun needs to know for hosting the website.
Arjun do you need any help with these item for the project plan? Are you on track
for 21 June? No. Arjun on track for 21 June 2006

Arjun , what are we utilizing our own or bu-pm-com?
Email from Gupta, Kanishka to CS632 students
Sorry for not clarifying. This mail only pertained to teams utilizing the "bu-
pm.com" site. You are welcome to use your own.
6 June 2006 For our team project will be using the "bu-pm.com" site.

Arjun, The instructions say we are to provide a link to your team member’s
paper/podcast for the Research.htm? How do we do this? Do we us the audio
blogger?

6 June 2006 The agreement with our team is that everyone will create their own
audio blog of their Research paper on the Team 2 Blog site created by Arjun. Arjun
can link the Team blog site to our web project. Below is the Team Blog information.

Blog                                                                             Info:
Blogname:                                              http://cs632team.blogspot.com/
Username:                                                                  cs632team
Pwd: 123456


Risk Management
       Identification, quantification, mitigation, contingency plan
As of 30 May 2006 kick off meeting this task was not assigned. It was agreed this
task would be discussed at a later date. (It’s possible that Patrick Dwyer or Aaron
Wong can assume this task but that has not been resolved.)
Patrick, are you able to take the Risk Management portion of the Project Plan?
Has anyone identified any risks as you went along?
6 June 2006 Patrick will take the risk management piece with the expected
completion date of 21 June.
Quality Standards & Quality Management approach. Email 1 June 2006 from Aaron
Wong accepted this task.
       Aaron do you need any help with these item for the project plan? Are you on
       track for 21 June? 6 June 2006 Yes, Aaron is on track for ECD of 21 June
       2006

Project Notebook
    Roles and Responsibilities
         (Linda will create this) Not done but will have it done on time.
        6 June 2006 Linda will have completed by 21 June 2006

        Team Blog


58
    (Team blog already created by Arjun) Done but not in the table of contents
       yet.
6 June 2006 This is done and ready for the table of contents.

       Team contact, directory, team meetings
      (Linda will document all team members and their contact information.)
      (Linda will find out what is meant by the term directory for the project
      notebook, and find out if the weekly agenda is updated and the content
      approved by each team member will suffice for the team meeting
      information. Team Contact is done and was sent to the team on Sunday 4
      June 2006. Team meeting times and day have been agreed upon. Not sure
      what is mean by directory but will find out.
6 June 2006 Contact information and team meetings done. Linda will check
information in the book for what makes up the directory contents.
       Weekly status report (Linda will submit a weekly status report to Fred Santino
          the following day of our Team Meetings
      Those in attendance on 30 May 2006 have agreed that Tuesday evenings at
      7:00 PM Central time is good for everyone. I submitted the team meeting
      minutes as promised by Thursday evening 1 June 2006.
      6- June 2006 Team informed that this was submitted to Prof Buresh and
      Fred Santino on Thurs. 1 June 2006.
      Linda will submit this weeks agenda discussion (6 June 2006) to Fred Santino
      and Prof Buresh by Thursday evening 8 June 2006

          Who does what, when (MS Project gives this report)
         Bill Carron will take care of this. (Bill this is in reference to the MS Project
         file. I’m noting it here so I make sure that I have all of the deliverables in the
         Table of contents. 6 June 2006 Bill on track for the 21 June 2006 deliverable.
         Needs information discussed previously from Arjun and Linda


        Final Report Project Table of Contents (page 108 of Schwalbe text)
         Linda Reed was assigned this task. I have the format but have not added
         anything yet. I will add what we have agreed upon in the Table of contents
         by next week’s team meeting.
         6 June 2006 Linda will have completed by 21 June 2006


Week         4       -         Software       Development          Life        Cycle:
Comment on the life cycle your team is using for the Web Project. Did you use a
methodology, such as Rapid Application Development (RAD), Agile Project
Management, or other related methodology? Comment on the appropriateness of your
selected methodology and any disadvantages that you have discovered. Also discuss how
your team made your selection.




59
This was the discussion question for week 4 regarding the “life cycle” methodology
we are using for the web project? Any advantages or disadvantages that we have
discovered? Any thoughts?

6 June 2006 As a team we discussed that we were using the Waterfall approach as in
our case is the most efficient technique for the software development.
On the other hand our overall project is going thru phases and is running in
parallel.

Week 4 - Issues:

You may want to use this opportunity to raise issues pertaining to your WEB PROJECT
or PODCAST PROJECT if any. Your instructor will read this and see if he/she can help.

This was the other question for week 4, any open issues for Team 2? This is an
ungraded discussion.

6 June 2006. We do not have any open issues at this time but will submit any
questions we have to Prof Buresh and Fred Santino.



6 June 2006 The meeting was closed and all agreed to the following Tuesday 13 June
for the next conference call at 7:00 PM central.



10.3 Week 5 Team Meeting
Team2 CS632
Conference call Tuesday 13 June 2006 7:00 PM Central Time.

The conference call was attended by all with the exception of William Carron who
has been deployed. The meeting lasted 37 minutes.

Note: Aaron will be out of town the week of 19 June but will be checking emails
when time permits.


Team Members:
1. William Carron
2. Arjun Vyas
3. Joong Lee
4. Linda Reed
5. Patrick Dwyer
6. Aaron Wong



60
Agenda Items:

13 June 2006 Aaron will be out ot town next week but will checke email as time
permits. Bill has been deployed to (I think Wisconsin) but will be checking in and
completing assignments but may not make the conference call.

13 June 2006 Arjun, in order to create the audio blog for our research paper to the
Team blog site we will need the phone number with area code and the pin number
you used to create the team blog.

Note from Aaron 12 June 2006

I'd used my own audio blogger account and posted it to my blogspot account. Then I
logged into the team blogspot account and created a new posting and pasted the
html text from the posting on my account and it includes the audio portion.

Response: 13 June: Arjun will create audio blog account for Team 2. (alternate
option) Aaron created a new intert and copies the HTML code from his individual
blog into this one.

13 June 2006 Final Project Guidelines
This information was taken from the Week 4 Updates for the course and Final
Project Guidelines: http://www.bu-pm.com/cs632/ (please check occasionally).
Although the Project deliverable can be found at http://www.bu-
pm.com/cs632/GradingRubricForProjectVersion2.pdf The Project guidelines has
specific for templates, etc. There is a lot of information so please review what format
they will be expecting for your assigned tasks.

http://office.microsoft.com/en-us/templates/TC010774551033.aspx

http://login.course.com/login/login.cfm?targeturl=http%3A%2F%2Fwww%2Ecour
se%2Ecom%2Fdownloads%2Fmis%2Fschwalbe4e%2Findex%2Ecfm%3F&appId
=ITPMProduct (This is the book’s companion web site for templates)

Response: 13 June 2006 Team will review the templates to see if they are applicable
to our project.

Web Team Roles

13 June 2006 You are required to submit Team Roles and Milestone targets for each
role/individual as
illustrated in this section.
We need to define each other roles and milestone target for each role? (Bill have you
defined the projects milestones by role as part of the project plan?)



61
1. William Carron
2. Arjun Vyas
3. Joong Lee
4. Linda Reed
5. Patrick Dwyer
6. Aaron Wong

Before you can manage a Web development team you have to know the players. It's
important to note that team composition is different from organization to organization,
project to project, and process to process. Your Web development team may not exactly
mirror the type that is described in this chapter (see the diagram below), but there will
undoubtedly be many similarities. The basic roles on a typical Web development team
remain relatively constant and typically include the following.

  Project stakeholder (also client or business owner)
  Project manager
  Producer
  Editor/copywriter
Information architect
  Graphic designer
  HTML developer
  Developer
  Tech lead
  Database administrator
  Quality assurance engineer

Response: 13 June 2006 the team discussed the various roles. Linda will implement
these in the Roles and Responsibilities deliverable.



Closure Report
A project does not end with the delivery and installation of the software; before it is
closed, it must be used for learning. Project closure analysis is one method to achieve this
goal. Following are some of the key takeaways from the Infosys approach to project
closure:
13 June 2006 Response: Linda will create an acceptance report.


Discuss Features and Functions and who has the expertise to complete these tasks.
Arjun will submit a list of High Level Features and create a task list for the web
development with duration time. Expected completion dates. (Has the list been
revised with the final features and functions?

6 June 2006 Arjun has discussed and has finalized the requirements. Arjun will
send out the final web features and a task list so Bill can update the MS project
WBS for Arjun’s web development piece.



62
13 June 2006 Bill do you have what you need from Arjun for the WBS?

13 June Response: Bill has been deployed but will continue to complete the assigned
tasks and check email. He was not able to attend the meeting tonight but will get his
assignments to me as soon as possible.


Our goal is to complete the Web project by 21 June 2006. Are we still on track for
21 June completion? Arjun, do you need any help from Aaron?
6 June 2006 No, Arjun will complete the task.
13 June 2006 Arjun is done with the web project he just needs to load it. Did Prof
Kanabar or anyone send you the subdomain information?

Note : Arjun has created a sub-domain called cs632s14t2.bu-pm.com. ( I tested it
today and it worked fine. Date completed 13 June 2006

13 June 2006 Response: The web project is up and running and ready for the teams
review.

Discuss and review the SCOPE Statement determine revisions if any or acceptance.
(Joong Lee is revising the scope statement) Joong how are the revisions on the scope
statement coming along?
6 June 2006 Joong’s expected completion date will be 21 June 2006.
13 June 2006 When you are done revising the scope statement please send it out to
the team for review as soon as possible and I will post it to the table of contents.

13 June 2006 Response: Joong is working the scope statement and will try to get me
the draft by this weekend.


Assign tasks per the SCOPE statement

(\See the WBS information below to be completed in MS Project by Bill Carron Bill,
how is the WBS coming along in MS project? Has the file been created? Do you
need any information from us to update it?

6 June 2006 Arjun will send the planning development and stages of the web pages,
etc. to Bill along with how much time it takes for each task. Example in 30 minute
time increments. Linda will do the same for the project management piece.
Example: How long does it take to initate conference calls, etc. Bill would like this
information from Linda and Arjun by our next weeks meeting of Tues 13 June
2006. Also the team is to send to Bill how long it takes to complete their deliverable
so all this information is adequately documented too.

13 June 2006 Do you have what you need from Linda for the WBS




63
13 June Response: Bill has been deployed but will continue to complete the assigned
tasks and check email. He was not able to attend the meeting tonight but will get his
assignments to me as soon as possible.


Assign deliverables for the final Web Project (80%)
If you are assigned to a deliverable please determine the duration needed and any
constraints to input into MS Project to include an expected completion date. Add
any additional assumptions.

13 June 2006 Did you all see the deliverable formats and templates they are looking
for with the Project? I sent the deliverable PDF fromProf Kanabar this weekend.
13 June 2006 Response: Yes, the team saw the deliverables from Prof Kanabar.


Business Case (see page 82-85 of Schwalbe text)
Assigned to Bill Carron Bill, how is the business case deliverable coming along, do
you need any help with it?
6 June 2006 Bill ECD (expected completion date is 21 June 2006
13 June 2006 When you are done revising the Business case please send it out to the
team for review and I will post it to the table of contents
13 June Response: Bill has been deployed but will continue to complete the assigned
tasks and check email. He was not able to attend the meeting tonight but will get his
assignments to me as soon as possible.


Scope Statement: Joong Lee
6 June 2006 Joong ECD (expected completion date is 21 June 2006
13 June 2006 When you are done revising the scope statement please send it out to
the team for review and I will post it to the table of contents
13 June 2006 Response: Joong is working the scope statement and will try to get me
the draft by this weekend.


Project Plan to include:


        Purpose/Background and approach Purpose/Background/approach and Scope
          statement drafts also coming soon.
        Goals and Objectives 13 June 2006 Done: Submitted for team review.
        Purpose/Background/approach and Scope statement drafts also coming soon.
The above items highlighted in yellow have been assigned to Joong Lee.
Joong do you need any help with these item for the project plan? Are you on track
for 21 June?
6 June 2006 Joong ECD (expected completion date is 21 June 2006



64
13 June 2006 When you are done revising the project please send it out to the team
for review and I will post it to the table of contents

13 June 2006 Purpose/Background/approach and Scope statement drafts also
coming soon.

13 June 2006 Response: Joong submitted the Goals and Objective for the team
review. If no request for revisions or comments for change.. Linda will post to the
table of contents. Joong is also working the scope statement and will try to get me
the draft by this weekend.


          Constraints/assumptions
          Related Sub projects/critical dependencies
          WBS (see scope statement information includes Appendix A suggested tasks)
          Schedule and milestones (MS Project)
          Tools and techniques to be uses
                   Technical
                   Non technical
The above items have been assigned to Bill Carron
Bill do you need any help with these item for the project plan? Are you on track for
21 June?
6 June 2006 Bill ECD (expected completion date is 21 June 2006

13 June 2006 Bill when you are done revising this section of the project plan it will
have to be combined with Joong’s section with the project plan documents.
13 June Response: Bill has been deployed but will continue to complete the assigned
tasks and check email. He was not able to attend the meeting tonight but will get his
assignments to me as soon as possible.



Budget for hosting: Hosting information submitted to team by Vijay Kanabar on
Sunday 29 May 06. Hosting with IX Web Hosting (grading rubic 40% for a
functioning website) Assigned to Arjun
Note: (Arjun has sent an email to Prof Kanabar on 30 May 2006 to clarify what
Arjun needs to know for hosting the website.
Arjun do you need any help with these item for the project plan? Are you on track
for 21 June?
6 June 2006 No. Arjun on track for 21 June 2006
13 June 2006 When you are done revising the Budget for hosting section please send
it out to the team for review and I will post it to the table of contents.
13 June 2006 Response: Arjun sent the budget via email on 13 June 2006 after the
conference call. The cost to host the web project is 12.95 per month.

Arjun , what are we utilizing our own or bu-pm-com?


65
Email from Gupta, Kanishka to CS632 students
Sorry for not clarifying. This mail only pertained to teams utilizing the "bu-
pm.com" site. You are welcome to use your own.
6 June 2006 For our team project will be using the "bu-pm.com" site.
13 June 2006 Arjun Any response regarding the subdomain. I did see your emails to
Prof Kanbar and Fred
Our domain has been created and I tested it today. (L Reed)
13 June 2006 Response: The team will review the website. Looks great Arjun! 


The instructions say we are to provide a link to your team member’s paper/podcast
for the Research.htm? How do we do this? Do we us the audio blogger?

6 June 2006 The agreement with our team is that everyone will create their own
audio blog of their Research paper on the Team 2 Blog site created by Arjun. Arjun
can link the Team blog site to our web project. Below is the Team Blog information.

Blog                                                                            Info:
Blogname:                                             http://cs632team.blogspot.com/
Username:                                                                 cs632team
Pwd: 123456

13 June 2006 Did everyone see the email from Prof Kanabar about the different
option for Podcast? Does that change our plan from creating our podcasts from the
team blog site? Also I sent a question to Fred Santino and asked if we would get
credit for posting to the Team blog as opposed to our individual blog for the
Research.htm paper. The reason I asked this question is because Week 4 states to
receive extra bonus consideration publish your blog to your individual blog site.

13 June 2006 Posting Our Web Proeject Deliverables: You're right there isn't a
specific assignment template for the final project as was done for the other
assignments.
The web project itself is uploaded to the webspace provided by Prof Kanabar. The
project documents should be posted on the team's blog. The grading will done from
those sources. This was described in the PDF file that gave the project instructions. I
hope that helps.

13 June 2006 Response: Linda will complete the table of contents will all the
deliverables and send to Arjun to post. I’m not sure how to post an attachment to
the Blog at this time. Arjun will upload to domain directory.


Risk Management
Identification, quantification, mitigation, contingency plan




66
As of 30 May 2006 kick off meeting this task was not assigned. It was agreed this
task would be discussed at a later date. (It’s possible that Patrick Dwyer or Aaron
Wong can assume this task but that has not been resolved.)
Patrick, are you able to take the Risk Management portion of the Project Plan?
Has anyone identified any risks as you went along?
6 June 2006 Patrick will take the risk management piece with the expected
completion date of 21 June.

13 June 2006 When you are done revising the risk management section please send
it out to the team for review and I will post it to the table of contents.
13 June 2006. Response: Patrick will try to have this Risk’s etc to me by this
weekend.


Quality Standards & Quality Management approach.

Email 1 June 2006 from Aaron Wong accepted this task.
Aaron do you need any help with these item for the project plan? Are you on track
for 21 June?
6 June 2006 Yes, Aaron is on track for ECD of 21 June 2006
13 June 2006 Aaron submitted the Quaality and Standards Document on Sunday 11
June 2006. Please review and submit your approval.
13 June 2006: Response: Aaron has completed the Quality documents and will be
reviewed by the team. If no comments or request for change Linda will post it to the
deliverables table of contents.

Project Notebook
     Roles and Responsibilities
(Linda will create this) Not done but will have it done on time.
6 June 2006 Linda will have completed by 21 June 2006
13 June 2006 When you are done revising the Project Notebook section please send
it out to the team for review and I will post it to the table of contents
13 June 2006 Response: Linda will be working these documents this weekend. A
draft has been created.

         Team contact, directory, team meetings
(Linda will document all team members and their contact information.) (Linda will
find out what is meant by the term directory for the project notebook, and find out
if the weekly agenda is updated and the content approved by each team member will
suffice for the team meeting information.
Team Contact is done and was sent to the team on Sunday 4 June 2006. Team
meeting times and day have been agreed upon. Not sure what is mean by directory
but will find out.
6 June 2006 Contact information and team meetings done. Linda will check
information in the book for what makes up the directory contents.
13 June 2006 Linda same as above


67
13 June 2006 Response: Linda will be working these documents this weekend. A
draft has been created.

        Weekly status report (Linda will submit a weekly status report to Fred
          Santino the following day of our Team Meetings
Those in attendance on 30 May 2006 have agreed that Tuesday evenings at 7:00 PM
Central time is good for everyone. I submitted the team meeting minutes as
promised by Thursday evening 1 June 2006.
6- June 2006 Team informed that this was submitted to Prof Buresh and Fred
Santino on Thurs. 1 June 2006.
Linda will submit this weeks agenda discussion (6 June 2006) to Fred Santino and
Prof Buresh by Thursday evening 8 June 2006
13 June 2006 I submitted 6 June 2006 team meeting notes on Friday instead of
Thursday.
13 June 2006. Linda to submit to Prof Buresh and Fred Santino on Thurs.

         Who does what, when (MS Project gives this report)
Bill Carron will take care of this. (Bill this is in reference to the MS Project file. I’m
noting it here so I make sure that I have all of the deliverables in the Table of
contents.
6 June 2006 Bill on track for the 21 June 2006 deliverable. Needs information
discussed previously from Arjun and Linda
13 June 2006 When you are done revising the Project Notebook section please send
it out to the team for review and I will post it to the table of contents.
13 June Response: Bill has been deployed but will continue to complete the assigned
tasks and check email. He was not able to attend the meeting tonight but will get his
assignments to me as soon as possible.


Final Report Project Table of Contents (page 108 of Schwalbe text)
Linda Reed was assigned this task. I have the format but have not added anything
yet. I will add what we have agreed upon in the Table of contents by next week’s
team meeting.
6 June 2006 Linda will have completed by 21 June 2006

13 June 2006 When you are done revising Table of content section please send it out
to the team for review before submitting for the Team.
Submitted the format to the team on 11 June 2006
13 June 2006 Response: The table of contents format was submitted to the team for
review. The response was favorable from the team.

Technical Documentation ( I missed this deliverable)

Technical Documentation that you are strongly encouraged to submit

13 June 2006 What kind of tools did we use for this project?


68
13 June 2006 Linda sent an email after the conference call to Arjun requesting this
information.

Design Specs and Code? Do you have this imformation documented? From Arjun I
received the DB Schema, Flow, Chart and Dlow Diagram 12 June 2006
13 June 2006 Linda received the DB schema, flow chart and flow diagram in Visio
from Arjun. I could not open the documents with Visio viewer. Sent email to Fred
Santino and Arjun to let them know.

1. Site map and user Manual (how to use your web application) Do you have this
imformation documented? Arjun: You can try zipping the file and sending it to me
at picardl@charter.net Tutorials (with screenshots) (EXCEEDING THE SIZE
LIMIT--I WILL NEED TO SEND THIS VIA A SEPERATE EMAIL)
13 June 2006 Response: Arjun will zip the file and send this to Linda via her home
email address

2. Quality Planning, Testing and QA evidence. (No need if you turned this in the
Project Management section.) Do you have this imformation documented?
13 June 2006 See Quality documents created by Aaron.

3. Technical Specifications (appendix a: http://www.bupm.
com/cs632/documents/KeyDeliverablesforProject.pdf) Do you have this imformation
documented?
13 June 2006 Linda received the DB schema, flow chart and flow diagram in Visio
from Arjun. I could not open the documents with Visio viewer. Sent email to Fred
Santino and Arjun to let them know.

4. Database Schema Do you have this imformation documented? (Yes received 12
June 2006)

13 June 2006 I missed the technical documents within the deliverable. Arjun will
send me what information he has created and I will work the text. He has the flow
chart and the database schema completed.
13 June 2006 Linda received the DB schema, flow chart and flow diagram in Visio
from Arjun. I could not open the documents with Visio viewer. Sent email to Fred
Santino and Arjun to let them know. The Visio plug-in did not work on my
computer.




69
10.4 Week 6 Team Meeting
Team CS632
Meeting Agenda
20 June 2006

Conference call Tuesday 20 June 2006 7:00 PM Central Time. Duration 51 minutes

Fred Santino had planned to attend but was not present. All team members
attended with the exception of Aaron. Aaron is out of town and will be checking
email when time permits

Note: Team2 is wrapping up some final documents. Linda will submit the completed
table of contents to Arjun who will post all of the documents. ECD: 21 June 2006


Team Members:
1. William Carron
2. Arjun Vyas
3. Joong Lee
4. Linda Reed
5. Patrick Dwyer
6. Aaron Wong


Agenda Items:

13 June 2006 Arjun, in order to create the audio blog for our research paper to the
Team blog site we will need the phone number with area code and the pin number
you used to create the team blog.

Response: 13 June: Arjun will create audio blog account for Team 2. (Alternate
option) Aaron created a new insert and copies the HTML code from his individual
blog into this one.

20 June 2006 Arjun, has this been created? I saw Aaron’s blog on the team site but I
couldn’t figure out where to find the HTML file in my individual blog to copy it
over to the team blog? Plan B Can someone walk me thru this? Or I can re-record
thru the audio blogger team site.




70
20 June Response: Arjun created the team blog site and sent the information to
Team 2 to complete their audio blog to the Team site.


Web Team Roles

13 June 2006 You are required to submit Team Roles and Milestone targets for each
role/individual as
Illustrated in this section.
We need to define each other roles and milestone target for each role? (Bill have you
defined the projects milestones by role as part of the project plan?)


Response: 13 June 2006 the team discussed the various roles. Linda will implement
these in the Roles and Responsibilities deliverable.

20 June 2006 Linda completed the Team Roles and Resp deliverable document.
20 June Response: This is done.


Closure Report

A project does not end with the delivery and installation of the software; before it is
closed, it must be used for learning. Project closure analysis is one method to achieve this
goal. Following are some of the key takeaways from the Infosys approach to project
closure:
13 June 2006 Response: Linda will create an acceptance report.

20 June 2006 Fred does the Project table of contents suffice as the closure report for
this project. I’ve reviewed the “Closing Projects” information on page 156.

20 June 2006 Response: This is not a documented deliverable but Linda will check
with Fred for the closure report.

Discuss Features and Functions and who has the expertise to complete these tasks.
Arjun will submit a list of High Level Features and create a task list for the web
development with duration time. Expected completion dates. (Has the list been
revised with the final features and functions?

13 June Response: Bill has been deployed but will continue to complete the assigned
tasks and check email. He was not able to attend the meeting tonight but will get his
assignments to me as soon as possible.

20 June: Bill please verify status of the WBS.




71
20 June 2006 Response: Bill completed the High Level WBS and will complete the
more detailed MS project file and submit to Linda on 21 June 2006.


Our goal is to complete the Web project by 21 June 2006. Are we still on track for
21 June completion? Arjun, do you need any help from Aaron?
6 June 2006 No, Arjun will complete the task.
13 June 2006 Arjun is done with the web project he just needs to load it. Did Prof
Kanabar or anyone send you the subdomain information?

Note: Arjun has created a sub-domain called cs632s14t2.bu-pm.com. (I tested it
today and it worked fine. Date completed 13 June 2006

13 June 2006 Response: The web project is up and running and ready for the teams
review.
20 June 2006. The web site is up and running and has been tested by Linda and
Joong.
20 June Response: This is done.

Discuss and review the SCOPE Statement determine revisions if any or acceptance.
(Joong Lee is revising the scope statement) Joong how are the revisions on the scope
statement coming along?
6 June 2006 Joong’s expected completion date will be 21 June 2006.
13 June 2006 When you are done revising the scope statement please send it out to
the team for review as soon as possible and I will post it to the table of contents.

13 June 2006 Response: Joong is working the scope statement and will try to get me
the draft by this weekend.

20 June 2006. Completed by Joong: Joong sent me the revised scope statement this
weekend for review. It’s ready for submission.
20 June Response: This is done.


Assign deliverables for the final Web Project (80%)
If you are assigned to a deliverable please determine the duration needed and any
constraints to input into MS Project to include an expected completion date. Add
any additional assumptions.

13 June 2006 Did you all see the deliverable formats and templates they are looking
for with the Project? I sent the deliverable PDF fromProf Kanabar this weekend.
13 June 2006 Response: Yes, the team saw the deliverables from Prof Kanabar.
20 June Response: All agree to seeing the deliverables.




72
Business Case (see page 82-85 of Schwalbe text)
Assigned to Bill Carron Bill, how is the business case deliverable coming along, do
you need any help with it?
6 June 2006 Bill ECD (expected completion date is 21 June 2006
13 June 2006 When you are done revising the Business case please send it out to the
team for review and I will post it to the table of contents
13 June Response: Bill has been deployed but will continue to complete the assigned
tasks and check email. He was not able to attend the meeting tonight but will get his
assignments to me as soon as possible.

20 June 2006 Bill sent me the Business Case this weekend and I will review it by our
conference call on Tuesday night.
20 June Response: This is done.

Project Plan to include:

Purpose/Background and approach Purpose/Background/approach and Scope statement
drafts also coming soon

June 2006
Completed by Joong and reviewed: Scope statement reviewed and ready for
submission
20 June Response: This is done.

20 June 2006
Completed by Joong and reviewed: Purpose and background reviewed and are
ready for submission
20 June Response: This is done.
20 June 2006 Completed by Joong and reviewed: Goals and Objectives reviewed
and are ready for submission
 20 June 2006 This is done.


Constraints/assumptions
20 June 2006 This is done.


Related Sub projects/critical dependencies
20 June 2006 Response: Bill will completed and send to the team on 21 June 2006
WBS (see scope statement information includes Appendix A suggested tasks)
   20 June 2006 Response. Bill will completed and send to the team on 21 June
       2006
Schedule and milestones (MS Project)
   20 June 2006 Response: Bill will completed and send to the team on 21 June
   2006



73
The above items highlighted in green have been assigned to Bill Carron
Bill do you need any help with these item for the project plan? Are you on track for
21 June?
6 June 2006 Bill ECD (expected completion date is 21 June 2006

13 June 2006 Bill when you are done revising this section of the project plan it will
have to be combined with Joong’s section with the project plan documents.

13 June Response: Bill has been deployed but will continue to complete the assigned
tasks and check email. He was not able to attend the meeting tonight but will get his
assignments to me as soon as possible.

20 June: Bill please verify status of the WBS.
20 June 2006 Response: Bill working and will submit by 21 June 2006

Tools and techniques to be used

20 June 2006 Done


Budget for hosting: Hosting information submitted to team by Vijay Kanabar on
Sunday 29 May 06. Hosting with IX Web Hosting (grading rubic 40% for a
functioning website) Assigned to Arjun
Note: (Arjun has sent an email to Prof Kanabar on 30 May 2006 to clarify what
Arjun needs to know for hosting the website.
Arjun do you need any help with these item for the project plan? Are you on track
for 21 June?
6 June 2006 No. Arjun on track for 21 June 2006

13 June 2006 When you are done revising the Budget for hosting section please send
it out to the team for review and I will post it to the table of contents.
13 June 2006 Response: Arjun sent the budget via email on 13 June 2006 after the
conference call. The cost to host the web project is 12.95 per month.

20 June 2006: Completed by Arjun
20 June 2006 Response: Done



Arjun, what are we utilizing our own or bu-pm-com?
Email from Gupta, Kanishka to CS632 students
Sorry for not clarifying. This mail only pertained to teams utilizing the "bu-
pm.com" site. You are welcome to use your own.
6 June 2006 For our team project will be using the "bu-pm.com" site.



74
13 June 2006 Arjun Any response regarding the subdomain. I did see your emails to
Prof Kanbar and Fred
Our domain has been created and I tested it today. (L Reed)
13 June 2006 Response: The team will review the website. Looks great Arjun! 
20 June Response: Done



The instructions say we are to provide a link to your team member’s paper/podcast
for the Research.htm? How do we do this? Do we us the audio blogger?

6 June 2006 The agreement with our team is that everyone will create their own
audio blog of their Research paper on the Team 2 Blog site created by Arjun. Arjun
can link the Team blog site to our web project. Below is the Team Blog information.

Blog                                                                            Info:
Blogname:                                             http://cs632team.blogspot.com/
Username:                                                                 cs632team
Pwd: 123456

13 June 2006 Did everyone see the email from Prof Kanabar about the different
option for Podcast? Does that change our plan from creating our podcasts from the
team blog site? Also I sent a question to Fred Santino and asked if we would get
credit for posting to the Team blog as opposed to our individual blog for the
Research.htm paper. The reason I asked this question is because Week 4 states to
receive extra bonus consideration publish your blog to your individual blog site.

13 June 2006 Posting Our Web Project Deliverables: You're right there isn't a
specific assignment template for the final project as was done for the other
assignments.

20 June 2006 (Email from Fred) The web project itself is uploaded to the webspace
provided by Prof Kanabar. The project documents should be posted on the team's
blog. The grading will be done from those sources. This was described in the PDF
file that gave the project instructions. I hope that helps.
20 June 2006 Discuss with Fred our options\
20 June 2006 Response: Arjun will post all the project deliverable documents.
Pending Bill’s deliverables Linda will submit to Arjun all the files within the tables
of contents by 21 June 2006.


13 June 2006 Response: Linda will complete the table of contents will all the
deliverables and send to Arjun to post. I’m not sure how to post an attachment to
the Blog at this time. Arjun will upload to domain directory.




75
20 June 2006 I need to discuss how to get these documents posted to the blog site or
where they need to be attached.

20 June 2006 The table of contents with the documents attached is completed for the
project deliverable with the exception of documents that are pending.

20 June 2006 Response: Done pending files from Bill.


Risk Management
Identification, quantification, mitigation, contingency plan

As of 30 May 2006 kick off meeting this task was not assigned. It was agreed this
task would be discussed at a later date. (It’s possible that Patrick Dwyer or Aaron
Wong can assume this task but that has not been resolved.)
Patrick, are you able to take the Risk Management portion of the Project Plan?
Has anyone identified any risks as you went along?
6 June 2006 Patrick will take the risk management piece with the expected
completion date of 21 June.
13 June 2006 When you are done revising the risk management sections please send
it out to the team for review and I will post it to the table of contents.
13 June 2006. Response: Patrick will try to have theseRisk’s etc to me by this
weekend.

20 June 2006 Patrick please provide status. 20 June Response: This is done

Quality Standards & Quality Management approach.
Email 1 June 2006 from Aaron Wong accepted this task.
Aaron do you need any help with these item for the project plan? Are you on track
for 21 June?
6 June 2006 Yes, Aaron is on track for ECD of 21 June 2006
13 June 2006 Aaron submitted the Quality and Standards Document on Sunday 11
June 2006. Please review and submit your approval.
13 June 2006: Response: Aaron has completed the Quality documents and will be
reviewed by the team. If no comments or request for change Linda will post it to the
deliverables table of contents.

20 June 2006 Completed by Aaron. No comments or suggestions were received.
20 June Response: This is done


Project Notebook
Roles and Responsibilities
(Linda will create this) Not done but will have it done on time.
6 June 2006 Linda will have completed by 21 June 2006



76
13 June 2006 When you are done revising the Project Notebook section please send
it out to the team for review and I will post it to the table of contents
13 June 2006 Response: Linda will be working these documents this weekend. A
draft has been created.

20 June 2006 Completed by Linda
20 June Response: This is done

Team contact, directory, team meetings
(Linda will document all team members and their contact information.) (Linda will
find out what is meant by the term directory for the project notebook, and find out
if the weekly agenda is updated and the content approved by each team member will
suffice for the team meeting information.
Team Contact is done and was sent to the team on Sunday 4 June 2006. Team
meeting times and day have been agreed upon. Not sure what is mean by directory
but will find out.
6 June 2006 Contact information and team meetings done. Linda will check
information in the book for what makes up the directory contents.
13 June 2006 Linda same as above
13 June 2006 Response: Linda will be working these documents this weekend. A
draft has been created.

20 June 2006. Completed by Linda
20 June Response: This is done

Weekly status report (Linda will submit a weekly status report to Fred Santino the
following day of our Team Meetings
Those in attendance on 30 May 2006 have agreed that Tuesday evenings at 7:00 PM
Central time is good for everyone. I submitted the team meeting minutes as
promised by Thursday evening 1 June 2006.
6- June 2006 Team informed that this was submitted to Prof Buresh and Fred
Santino on Thurs. 1 June 2006.
Linda will submit this weeks agenda discussion (6 June 2006) to Fred Santino and
Prof Buresh by Thursday evening 8 June 2006

13 June 2006 I submitted 6 June 2006 team meeting notes on Friday instead of
Thursday.
13 June 2006. Linda to submit to Prof Buresh and Fred Santino on Thurs.
20 June 2006 Completed by Linda 21 June 2006 Sent to Prof Buresh and Fred
Santino



Who does what, when (MS Project gives this report)




77
Bill Carron will take care of this. (Bill this is in reference to the MS Project file. I’m
noting it here so I make sure that I have all of the deliverables in the Table of
contents.
6 June 2006 Bill on track for the 21 June 2006 deliverable. Needs information
discussed previously from Arjun and Linda
13 June 2006 When you are done revising the Project Notebook section please send
it out to the team for review and I will post it to the table of contents.
13 June Response: Bill has been deployed but will continue to complete the assigned
tasks and check email. He was not able to attend the meeting tonight but will get his
assignments to me as soon as possible.

20 June 2006 Bill please update your status of the MS project
20 June 2006 Response: Bill working and will submit by 21 June 2006


Final Report Project Table of Contents (page 108 of Schwalbe text)
Linda Reed was assigned this task. I have the format but have not added anything
yet. I will add what we have agreed upon in the Table of contents by next week’s
team meeting.
6 June 2006 Linda will have completed by 21 June 2006

13 June 2006 When you are done revising Table of content sections please send it
out to the team for review before submitting for the Team.
Submitted the format to the team on 11 June 2006
13 June 2006 Response: The table of contents format was submitted to the team for
review. The response was favorable from the team.

20 June 2006 Completed: Linda submitted a draft to the team on Friday 16 June
2006. I will need to update the table of contents with the documents I received this
weekend.

20 June 2006 Response: Linda will update the table of contents when Bill sends his
files 21 June 2006


Technical Documentation (I missed this deliverable)

Technical Documentation that you are strongly encouraged to submit

13 June 2006 What kind of tools did we use for this project?
13 June 2006 Linda sent an email after the conference call to Arjun requesting this
information.

Design Specs and Code? Do you have this information documented? From Arjun I
received the DB Schema, Flow, Chart and Flow Diagram 12 June 2006




78
13 June 2006 Linda received the DB schema, flow chart and flow diagram in Visio
from Arjun. I could not open the documents with Visio viewer. Sent email to Fred
Santino and Arjun to let them know.

20 June 2006 Arjun recreated the Visio documents into JPG. I can open them now.
20 June 2006 Response: This is done.

1. Site map and user Manual (how to use your web application) Do you have this
information documented? Arjun: You can try zipping the file and sending it to me
at picardl@charter.net Tutorials (with screenshots) (EXCEEDING THE SIZE
LIMIT--I WILL NEED TO SEND THIS VIA A SEPERATE EMAIL)
13 June 2006 Response: Arjun will zip the file and send this to Linda via her home
email address

20 June 2006 Completed by Arjun.
20 June 2006 Response: This is done.

2. Quality Planning, Testing and QA evidence. (No need if you turned this in the
Project Management section.) Do you have this information documented?
13 June 2006 See Quality documents created by Aaron.

20 June 2006 Completed by Aaron.
20 June 2006 Response: This is done.


3. Technical Specifications (appendix a: http://www.bupm.
com/cs632/documents/KeyDeliverablesforProject.pdf) Do you have this information
documented?
13 June 2006 Linda received the DB schema, flow chart and flow diagram in Visio
from Arjun. I could not open the documents with Visio viewer. Sent email to Fred
Santino and Arjun to let them know.

20 June 2006 Completed by Arjun.
20 June 2006 Response: This is done.

4. Database Schema Do you have this information documented? (Yes received 12
June 2006)

13 June 2006 I missed the technical documents within the deliverable. Arjun will
send me what information he has created and I will work the text. He has the flow
chart and the database schema completed.
13 June 2006 Linda received the DB schema, flow chart and flow diagram in Visio
from Arjun. I could not open the documents with Visio viewer. Sent email to Fred
Santino and Arjun to let them know. The Visio plug-in did not work on my
computer.
20 June 2006 Completed by Arjun.


79
20 June 2006 Response: This is done.



10.5 Weekly Status Report Week 3 thru 6 are contained in the meeting sections



11 TECHNICAL DOCUMENTATION

11.1 Technical Specifications

Executive summary

        One-time Design and Development Costs: $1,000.00
        Recurring Fees: $12.95/month Hosting
        Project Start Date: May 2006
        Project End Date: June 2006
        Project Duration: 6 weeks


11.2 Technical Objectives

        This project purpose is to transform the cumbersome email system to a database
         driven system. A database system would allow the conference chair to print the
         data dynamically as well as allowing the system to be more robust and to gain
         enhanced features
         (Current Website:http://www.bu.edu/met/news/project_management/#)
        Provide a searchable archive to research abstracts-podcasts-videocasts as well as
         publishing PDF files from students taking CS632 on the following website
         (http://www.bu-pm.com/cs632/research.htm)
        Provide a web interface that will allow the conference attendees to register for the
         project on line
        Allow the conference chair to manage the conference though the Web interface.
        Display the Project Management conference events data.


11.3 Site Overview

        The site will contain the following major areas:
        Registration Information
        Calendar of Events
        State ID
        Conference Chair administration login



80
11.4 Hosting

        Hosting Fees: $12.95/ month
        Time: 3 weeks to configure Web server
        The hosting environment will be configured by Kanishka Gupta, of Boston
         University (bu-pm.com). Team 2 sub-domain cs632s14t2.bu-pm.com created by
         Arjun Vyas.
        Hardware specifications have been provided to the hosting provider data center.
        Operating system, Web server and database software will be loaded onto the
         servers by the hosting site system administrator according to specifications.
        Once the hosting site server is set up according to specification it will be tested.
         Once testing is complete Arjun Vyas will be migrate the web project development
         pages from the production server to the hosted environment.




11.5 Site Map and User Manual

HOME PAGE




81
REGISTRATION FORM




REGISTRATION SUBMISSION
CONFIRMATION DIALOG BOX



REGISTRION          FORM:
VALIDATIONS




82
VIEW EVENTS CALENDAR




ADMIN LOGIN




ADMIN MENU




83
ADMIN MENU>>   MANAGE
EVENTS




ADMIN MENU>> MANAGE
EVENTS>> ADD EVENT




ADMIN MENU>> MANAGE
EVENTS>> MODIFY EVENT




84
ADMIN     MENU>>    VIEW
REPORT (BY EVENT)




ADMIN    MENU>>     PRINT
REGISTRATION (BY EVENT)




85
ADMIN    MENU>>   PRINT
REGISTRATION        (BY
EVENT)>>PRINT




86
11.6   Flow Chart




87
11.7 Database Schema




88