Compiled Deliverable Set 2

Document Sample
Compiled Deliverable Set 2 Powered By Docstoc
					                    Project Connect
                       VoIP Pilot
_____________________________________________________________________________________________________________________


                            Cranston Bigler & Ice
                                         January 18, 2013



                                               Presented By:

                                          Ace Consultants
                                               (Team 06)
                                             Stephen Alesi
                                          Dennis Frankenfield
                                              Scott Serok
                                              Lev Soroka
                                            Nicholas Stuart




                                                         1
                                   Project Connect
                                   October 2, 2009


                               Table of Contents


Planning

      Team Contract…………………………………………………………………………………………..……..3-4

      Stakeholder Register…………………………………………………………………………………..……….5

      Stakeholder Strategy………………………………………………………………..………………………6-7

      Gantt Chart………………………………………………………………………………………………….………8

      Cash Flow Report…………………………………………………………………………………………...9-12

      Resource Usage Report…………………………………………………………………………………..…13

      Issues and Assumptions Log……………………………………………………………………………...14

      Quality Tool (Pareto Diagram)………………………………………………………………………….15

Executing

      Responsibility Assignment Matrix (RAM)……………………………………………………………16

      Agenda for a Project Team Meeting…………………………………………………………………..17

      Milestone Reports……………………………………………………………………………………………..18

      Prioritized Risks…………………………………………………………………………………………….19-20

      Risk Register………………………………………………………………………………………….…………..21

      Probability/Impact Matrix………………………………………………………………………….………22

      Presentation Addressing Challenges…………………………………………………………………23

      Prototype Screens and Project Website

            Prototype Screens……………………………………………………………………………...24-25

            Project Website………………………………………………………………………………..26-27

      Intermediate Project Presentation…………………………………………………………….28-29

                                         2
                                            Project Connect
                                            October 2, 2009

                                           Team Contract
Team Procedures

1. Meetings will occur when necessary to help the team gain a better understanding of their
   deliverables or any issues that may arise. Prior to meetings a meeting agenda will be sent out to
   inform of any questions and additional details. If meetings need to be cancelled there must be a 24
   hour notice before cancellation.


2. Communication to the team and any third party individuals will be communicated by the use of
   email, phone, and/or face to face. This will help to inform each member of team meetings,
   announcements, updates, reminders, and any problems.


3. Decisions will ultimately be decided as a team by consensus. If a consensus cannot be reached as a
   team the group leader, Lev Soroka, will lead as a mediator.


4. Agendas and planning will be the responsibility of each member. Each member will be responsible
   for completing their tasks in a timely manner. Lev Soroka will be in charge of setting due dates and
   making arrangements for meetings and times.


5. Record keeping for meetings will be recorded by means of writing and recording. After the meeting
   is adjourned it will be a selected member’s responsibility to type the meeting minutes and send
   them to another group member for approval. After the minutes have been approved they must be
   sent out before 24 hours to Michael Hayes and Kristen O’Shea by email.


Team Expectations

Work Quality

1. Project standards will be agreed upon prior to the start of the project. As a team, it will be our
   responsibility to make sure that quality is in our portion of work. To make sure we maintain high
   quality standards, before submission, our team will review all of the deliverables to check for any
   issues or corrections that may be needed.


Team Participation

1. Cooperation is expected from every member. Therefore, it is the responsibility for the group leader,
   Lev Soroka, to distribute work equally to the team and ensure cooperation.


2. We encourage and will accept any ideas or strategies from all group members. Every team member
   will have equal responsibilities.

                                                    3
                                              Project Connect
                                              October 2, 2009

Personal Accountability

1. Attendance for meetings will be mandatory by all group members. Exception to this rule is
   legitimate prior engagements. If a group member is absent for a meeting it will be their
   responsibility to obtain any information that they may have missed.


2. Participation at meetings will also be a requirement from every group member. Before the meeting
   we will discuss who will be responsible for asking questions and taking meeting minutes.


3. Deadlines for deliverables will be set by Lev Soroka. If a team member cannot or is not capable of
   fulfilling their duties it will be their responsibility to either ask another team member for help or to
   inform the group leader of this issue.


4. Communication with other members is strongly encouraged to help gain a better insight if a
   problem occurs during the creation of their deliverables. During class time we will check where we
   are and how far we need to go to complete our deliverable(s).

Consequences for Failing to Follow Procedures and Fulfill Expectations

1. Everyone on the team is required to follow these procedures and expectations. They are also
   required to act as a team.


2. If a group member is not compliant with these procedures and expectations they will be given three
   warnings before we inform superior individuals (learning assistant or the professor).From there they
   may be terminated from the group.

By signing this contract I have agreed that…
a) I participated in formulating the standards, roles, and procedures as stated in this contract.
b) I understand that I am obligated to abide by these terms and conditions.
c) I understand that if I do not abide by these terms and conditions, I fully understand the consequences
    that may occur.

Full Name

___________________________________________________date__________________

___________________________________________________date__________________

___________________________________________________date__________________

___________________________________________________date__________________

___________________________________________________date__________________
                           Stakeholder Register for Project Connect

                                                     4
                                         Project Connect
                                         October 2, 2009



Name                  Position            Internal/External   Project Role              Contact Information

Steve Alesi           Project Team        Internal            Business Analyst          Sca5056@psu.edu
                      Member

Nick Stuart           Project Team        Internal            Logistics                 Nps5031@psu.edu
                      Member

Scott Serok           Project Team        Internal            Development               Sas5437@psu.edu
                      Member

Lev Soroka            Project Team        Internal            Project Manager           Los5045@psu.edu
                      Member

Dennis Frankenfield   Project Team        Internal            Testing and Quality       Dpf5027@psu.edu
                      Member

Michael Hayes         Sponsor             External            Sponsor                   Hayes_Michael@bah.com

Sharon Cranston       Pilot Project       External            Deputy Chief              SCranston@CBI.com
                      Manager                                 Information Officer
                                                              (DCIO)

Henry Thornton        Site Leader         External            Boston Office Leader      HThornton@CBI.com

Genevieve Rose        Site Leader         External            Omaha Office Leader       GRose@CBI.com

Laura Claxton         Pilot Project       External            Aid Pilot Project         LClaxton@CBI.com
                      Assistant                               Manager

Boston Office         Satellite Office    External            Pilot Location            n/a

Omaha Office          Satellite Office    External            Pilot Location            n/a

Leroy Johnson         Purchasing Agent    External            Help with equipment       LJohnson@CBI.com
                                                              and materials receiving



                        Stakeholder Management Strategy

                                                5
                                      Project Connect
                                      October 2, 2009



Name              Level of Interest   Level of Influence   Potential Management Strategies

Michael Hayes     High                High                 Michael is a good sponsor who is very
                                                           knowledgeable in the IT project area. He
                                                           doesn’t always know what he wants but knows
                                                           what other IT programs are doing.

Sharon Cranston   High                High                 Sharon is very knowledgeable in the IT field
                                                           and has been placed in charge of the pilot.
                                                           She seems very helpful and willing to do what
                                                           it takes to get this project done right and on
                                                           time.

Henry Thornton    High                Low                  Henry is in charge of the Boston office, he
                                                           seems to feel his office produces better than
                                                           the others keep him informed of pilot
                                                           information as necessary. Henry is a
                                                           micromanager, to keep him happy weekly
                                                           updates will be sent to members.

Genevieve Rose    High                Low                  Genevieve is in charge of the Omaha office,
                                                           she is a very timid woman who seems to let
                                                           her employees do and think as they please. In
                                                           order to get a true reading from her and her
                                                           office, personal visits may be necessary.

Laura Claxton     Low                 Low                  Laura is Sharon’s assistant, she will be
                                                           supporting the project as best she can but will
                                                           likely need to report to Sharon with almost
                                                           everything, be sure to keep Laura and Sharon
                                                           informed so there is no misinformation.




Leroy Johnson     Low                 Low                  Leroy is in charge of regional purchasing, he is
                                                           in charge of lots of purchases and deliveries.


                                               6
                       Project Connect
                       October 2, 2009

                                         He has a lot going on and doesn’t seem very
                                         interested in our project, be sure to check up
                                         on his work frequently to ensure things are
                                         being delivered on time.

Boston Office   High   Low               The Boston office seems very excited about
                                         the installation of VOIP but will have slightly
                                         more (25) people then initially planned for.
                                         The employees seem very accepting of this
                                         change over.

Omaha Office    Low    Low               The Omaha office is very resistant to VOIP due
                                         to a lead designer having a bad experience. He
                                         has been spreading negative word about VOIP.
                                         Additional training and support may be
                                         required in order to gain acceptance of a new
                                         system by showing the ease and usefulness of
                                         the transition.




                       Gantt Chart



                             7
Project Connect
October 2, 2009




      8
  Project Connect
  October 2, 2009

Cash Flow Report




        9
Project Connect
October 2, 2009




      10
Project Connect
October 2, 2009




      11
Project Connect
October 2, 2009




      12
    Project Connect
    October 2, 2009

Resource Usage Chart




          13
                                                                   Issue Log & Assumptions
                                                                                                                          Priority
Issue #                                               Impact on Project     Date Reported   Reported By    Assigned To               Due Date      Status      Comments
                      Issue Description
                                                                                                                          (M/H/L)

            Better understanding of requirements        Slows down the
  1                                                                          Sep/28/09      Lev Soroka     Lev Soroka       M        Sep/30/09   Completed
                                                            process

          Required personnel to complete successful
                                                       May cause extra                                                                                            What
                           pilot                       expenses or stop                                                                                         personnel
  2                                                                          Sep/29/09      Nick Stuart    Nick Stuart       H       Oct/2/09    Completed
                                                          the project                                                                                         should be used

                                                                                                                                                           Software would
                                                       Causing delays in                                                                                   not let save the
  3                                                                          Oct/22/09      Scott Serok    Scott Serok       L       Oct/23/09   Completed
                                                       planning process                                                                                      work, which
                 Project Software problems
                                                                                                                                                           cause set backs

                                                                                                                                                              Establish good
                                                      May cause delays or
  4           Receiving support from the client                              Oct/27/09      Lev Soroka         PM            H       Nov/01/09   In process    connection
                                                      negative feedback
                                                                                                                                                               with clients

                                                                                                                                                             Research and
                                                        May not have                                                                                        conduct proper
                                                                                               Dennis         Dennis
  5             Adjusting stakeholder analysis          proper info for      Oct/27/09                                      M        Nov/01/09   In process   analysis for
                                                                                            Frankenfield   Frankenfield
                                                           analysis                                                                                              new
                                                                                                                                                             stakeholders

                                                      May cause delays or                                                                                     Team needs to
  6             Adjusting to changes in scope           slow down the        Oct/27/09      Nick Stuart    Nick Stuart      M        Nov/01/09   In process    be ready for
                                                           execution                                                                                           the changes




                                                                                     14
Quality Tool (Pareto Chart)




            15
Responsibility Assignment Matrix (RAM)




                  16
                                              Project Connect
                                              October 2, 2009

                               Agenda for Project Team Meeting
                           Booz Allan Hamilton CBI – VPN Integration Pilot

                                                  Team 6

                                           Progress Meeting 2

                                                10/27/09

Meeting Objective: To clarify current misconceptions and uncertainties that have become relevant,
along with updating current progress of deliverables set 2.

Agenda:

       Clarify any questions present on the project.
       Review what has been completed thus far.
       Ask relevant questions on current material.
       Arrange next teleconference.

Action Item                                                Assigned To           Due Date

Information regarding stakeholder analysis:                Dennis Frankenfield   10/27/09

-In Stakeholder Strategy, what are some typical real
life issues that need to be solved?

Information regarding risk register:                       Lev Soroka            10/27/09

-Risk owner is the person responsible for the risk.

Would essentially the PM be responsible for the
people who are working with the risk?

-To what extent should the risks be calculated in the
project cost reserves



Possible Date and times for the next meeting: to be determined during the meeting




                                                      17
  Project Connect
  October 2, 2009

Milestone Report




        18
                                             Project Connect
                                             October 2, 2009

                                           Prioritized Risks
Ranking        Potential Risk

1              Conflicts within international regulations

2              Conflicts with international social time frames

3              Security issues of the new system

4              Proper planning

5              Underestimating product

6              Having the right people for the execution

7              Receiving feedback from the client

8              Effectively providing support for the pilot

9              Testing out the pilot

10             Clear scope requirements



During integration and entire project execution each potential risk will be carefully investigated and
controlled our team will do everything from preventing the risk and clearly labeling the possible
outcomes.

     1. Due to the requirements of Project Connect the number one potential risk may lay
        within international regulations. For such pilots it is very important to research and
        accommodate each regulation and requirement for this project to succeed.
     2. The second major risk that may be involved is with conflicts between international social
        time frames. Such pilots may need on site work and time frames will not always work
        for the contractor and the client, which may result in loosing time. Proper planning and
        management is required to make work go smoothly.
     3. Security issues with the new system may also become one of the main risks in Project
        Connect. A Good amount of work shall be put into investigating and testing out the
        Pilot.
     4. Proper planning is one of the most important criteria for the project. It will be most
        important to execute proper planning, for the project and to make sure every
        requirement is fulfilled.
     5. Underestimating the product might cause errors in the cost estimate. A good amount of
        time and research shall be put in to the proper estimates.


                                                    19
                                     Project Connect
                                     October 2, 2009

6. Having the incorrect amount of people or improper personnel may cause project funds
    to be wasted, or may cause the project to be executed incorrectly. It may not fulfill the
    requirements due to improper staff.
7. Receiving feedback from the clients is a very important aspect that may help to better
    integrate the pilot. Feedback will help label the areas that require improvements for the
    contractor and the pilot.
8. Some of the major requirements of Project Connect are providing support to the clients
    such as telephone help desk as well as onsite support. Our team will concentrate on this
    to better provide support to the client.
9. Testing out the pilot may become a risk, due to the many office locations and various
    time frames. However, during testing it is important to completely test the pilot and
    make sure everything works properly.
10. There may be some probability of having a project slow down or missing deadlines
    without having proper scope requirements. The requirements have to be clear and have
    to be realistic in order to prevent this problem from occurring. Our team will pay close
    attention to the requirements and ensure everything is in realistic bounds.




                                           20
Project Connect
October 2, 2009

Risk Register




      21
      Project Connect
      October 2, 2009

Probability/Impact Matrix




            22
           Project Connect
           October 2, 2009

Presentation Addressing Challenges




                 23
                                            Project Connect
                                            October 2, 2009

                           Prototype Screens and Project Website
                                               Prototype

The prototype that our team had to deal with was a reference guide for a pilot user to use their VoIP
phone from virtually anywhere with a broadband connection.

        1)        We started with a webpage that they could download this application, named Ace IP
                  Communicator and can be downloaded from AceIPCommunicator.com.




        2) After downloading this application we give the user a brief overview of how to login and get
started. For the users convience we made the username and password the same username and
password that they would use at work.




                                                   24
                                              Project Connect
                                              October 2, 2009

        3) After the login process the user has a brief setup process that can be done in five steps, listed
in the powerpoint. The user will be able to access the phone center. The phone center allows the pilot
user to access there VoIP phone anywhere with a broadband connection and a USB Headset. Another
convienient feature is that the extension of their VoIP phone online will have the same extension they
have at work.




                                           Project Website




                                                     25
                                            Project Connect
                                            October 2, 2009

Home Page (www.personal.psu.edu/nps5031): The home page is the starting point of our website
which hosts a variety of information and documents. We have an about us section on this page as well
as a description of our website.




Deliverables 1 and Deliverables 2: Deliverables 1 and Deliverables 2 has all of our deliverables from
deliverables set 1, you can click on the deliverable name to open the item individually




                                                                    Contact Us: The contact us screen
                                                                    has a roster of everyone on our
team as well as email addresses for easy communication.


                                                   26
          Project Connect
          October 2, 2009




Intermediate Project Presentation



                27
Project Connect
October 2, 2009




      28
Project Connect
October 2, 2009




      29

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:0
posted:1/18/2013
language:Latin
pages:29