Website Tutor Website Project Kick-off Meeting

Group: Nguyễn Thanh BìnhĐặng Văn TrungNguyễn Minh Tuấn

Agenda

• Project Overview• Stakeholder and Team Organization• Estimation Effort and Majors Deliverables• Project Communication and Escalation• Hardware and Software Matter• Risks Management• Project Acceptance

Project Overview

• Project Description– Create a online tutoring website to supports users who want to

registration teaching or looking for a tutor for their children.

• Project Scope– Website has 6 pages: Home, Introduction, Procedure, Price, News,

Contact– User management: Member registration, Login and logout, Edit Profile– Class and tutor management: Finding class and tutor register, accept

class and tutor– News management– Support browsers: Chrome, FF 15.0 Windows, IE 9 Windows, IE8

Windows– Webfarm environment: IIS7.

Project Overview (Cont.)

• Project Objective # Objective Success factor

1 Delivery deviation Almost deliveries are sent on time as plan. In the event

there is delay, the max delay is one day.

Final delivery must be on time.

2 Project acceptance No blocker and critical bug, others bugs not over 20 bugs

3 Scope complete All functions in requirement specification in scope must be completed.

4 Customer satisfaction Achieved

Stakeholder and Team Organization

Stakeholder and Team Organization(Cont.)

• Roles and Responsibilities # Role Responsibility

1 Program manager (PGM) • Responsible for Customer meeting in strategy level• Support project team in term of technical consultant and resources management

2 Client • Provide all materials and answers about requirement to project team.

• Check the product and provide feedbacks to project team as plan.

• Perform UAT and feedback

3 Project manager (PM) • Setup the project.

• In charge of Project management, Requirement Management and Resources management

• Responsible for the Project Deliverables which must be met the customer requirement regarding Security, Quality and Timeline

4 Business Analyst (BA) • Establish project planning for business analysis part

• Understand business process management and business requirements of the customers and translate them to specific software requirements.

• Document and analyze the required information and data.

• Effectively communicate with internal teams and external clients to deliver functional requirements like GUI, screen and interface designs.

Stakeholder and Team Organization(Cont.)

• Roles and Responsibilities

# Role Responsibility

5 Team Leader (TL) • Make detail estimation

• Analyze requirements and develop project's architectural design

• Establish project planning for development part

• Discuss and handle all technical issue with customer externally and team member internally

• Perform code review

• Directly communicate with client to solve the technical issues

• Build and deployment website6 Developers • Study requirements and system design

• Research new technologies

• Implement software components

• Perform unit tests

• Perform code review

• Fix bugs7 QC engineers • Develop/revise test cases, test data, and test scripts

• Register bugs

• Perform testing

• Participate in meetings and training sessions8 IT • Support setup server, software requirement for project team…

Stakeholder and Team Organization (Cont.)

• Stakeholder involvement

# RoleInvolvement

Proposal Inception Planning Construction Release & Closure

1 Program manager (PGM)

None High High Medium Medium

2 Client High Medium High Medium High

3 Project Manager (PM) None High High Medium High

4 Business Analyst (BA) High High High High Low

5 Technical Team Leader

None High High High Medium

6 Developer None None None High Low

7 QC engineers None None Medium High High

8 IT None None Low None None

Estimation Effort and Majors Deliverables

• Estimation Effort: – The project development team consist of 4 Developer (excluding PM), 1

BA, 1 QC Engineer– Total budget: 103 MDs

• Work plan and schedule– Project start date: 24-Dec-2012– Project expected end date: 15-Mar-2013

Estimation Effort and Majors Deliverables

• Milestones Plan# Milestone Milestone Description Complete

1 Project kick-offGather project team, introduce project and plan, officially start project

23-Dec-12

2 User requirement specification finalization

Deadline for final requirement baseline 24-Dec-12 – 26-Dec-12

3 Technical Design finalization Deadline for final technical design baseline 27-Dec-11 to 31-Dec-12

4 Development framework and layout Build framework follow technical design and design layout 01-Jan-13 to 16-Jan-13

5 Development front end website Implement feature follow requirement and design document 17-Jan-13 to 25-Jan-13

6 Development back end website Implement feature follow requirement and design document 25-Jan-13 to 4-Feb-13

7 Testing and fix bug Testing and fix bug 05-Feb-13 to 28-Feb -13

8 UAT Client execute test and project team support issues 7-Mar-13 to 14-Mar-13

9 Project Closure Time for starting Project Closure phase 15-Mar-13

Hardware & Software Matter

• Hardware:Currently team will be provided 3 PC for developing and 1 Server PC with configuration below

• Software: All PC must setup developing environment with software list below– Visual studio 2010 SP1.– SQL server 2008.– Microsoft expression studio 4.– Web browser: Safari, Mozilla Firefox, IE9 , Google Chrome.

# Resource Description Purpose Qty Responsible Provider

1 PC demo server with 8GB RAM at least Demo to Client 1 IT

2 PC for developer with: Processor: Intel Core i3, Ram: At

least 4Gb, OS: Windows 7 x64

Development 3 IT

3 PC for QC with at 4Gb at least Testing 1 IT

Risks Management

# Risk Category Probability Impact Effect Mitigation Strategy1 Scope Creep Development High High Delay Schedule/

Increase CostFollow change management plan

2 Schedule

Overrun

Planning High High Delay Schedule Progress reporting with controls

3 Budget

Overrun

Planning High High Increased Cost Progress reporting with controls

4 Requirements not met

Development Medium Medium Delay Schedule Perform Conditions of Satisfaction, Requirements breakdown structure, Customer involvement in all phases

5 Users resist new system

Testing Medium High Delay Schedule Include user input in requirements gathering and design phase

6 Poor Quality, Buggy Software

Testing Medium Medium Delay Schedule Ensure thorough testing strategy

7 Testing reveals significant flaw in design logic

Design Medium High Delay Schedule/ Increase Cost

Implement code review process

• Project Acceptance Objective– Ensure the Project Development team acknowledges the customer expectation on Project Deliverables– Avoid surprising at the end of the project to ensure high level customer satisfaction

• Functional/ Non-Functional Criteria

Project Acceptance

Criterion Description of Acceptance

Functional Complete All functions in requirement specification and in scope must be

completed.

All functional test cases must pass

Documentation All user guide made for the website must be completed

Defects No critical defects in the released product

Other defects must meet release criteria as mutually define

THANK YOU FOR YOUR ATTENTION!THANK YOU FOR YOUR ATTENTION!