Esprit Rock

PROJECT PLAN Project Name

PROJECT PLAN

Project Name: JKUAT Nairobi CBD Mobile Learning Platform
Project Manager: BRIAN PONDI
Project Team: JOAN TARUS
ANDREW KYALO
RUTH OMAYO
Version: 1.3
Issue Date:29/3/2018

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

Prepared by: Joan Tarus

Table of Contents
TOC o “1-3” h z u 1.0 Executive Summary PAGEREF _Toc515308877 h 11.0.1 Statement of Work PAGEREF _Toc515308878 h 11.0.2 Objectives PAGEREF _Toc515308879 h 21.0.3 Constraints PAGEREF _Toc515308880 h 21.0.4 Assumptions PAGEREF _Toc515308881 h 22.0 Scope Overview PAGEREF _Toc515308882 h 32.0.1 Work Breakdown Structure PAGEREF _Toc515308883 h 32.0.2 Business scope PAGEREF _Toc515308884 h 32.0.2 Scope Management Plan PAGEREF _Toc515308885 h 43.0 Budget Overview PAGEREF _Toc515308886 h 53.0.1 Budget Management PAGEREF _Toc515308887 h 54.0 Project Team PAGEREF _Toc515308888 h 54.1 Project Team Management PAGEREF _Toc515308889 h 65.0 Project Schedule PAGEREF _Toc515308890 h 65.0.1 Schedule Management PAGEREF _Toc515308891 h 66.0 Communication Plan PAGEREF _Toc515308892 h 97.0 Risk Management PAGEREF _Toc515308893 h 128.0 Monitoring and Controlling Plan PAGEREF _Toc515308894 h 129.0 Project Plan Documents Summary PAGEREF _Toc515308895 h 1310.0 Approval PAGEREF _Toc515308896 h 13
1.0 Executive SummaryThis document is a Software Project Management Plan (SPMP) for the development of a Mobile Learning Platform. This plan provides information regarding the project pertaining to the project organization, managerial process, technical process scheduling and budget. The SPMP is the controlling document for managing this project and will be maintained referenced in order to satisfy project requirement.

The project is to develop a JKUAT mobile learning application to make education and training available on the go-anytime and anywhere, at your own convenience. The intended audience are the students and the lecturers.

There has been the issues of students not knowing the date of exams, there time table, when CATs are being taken. Other problems are issue of jam hence not making it to lectures on time. This helps students who are employed and cannot make it to class on time or are on travel duties.

It will help the lecturers mark attendance of the students and the distribution of course lectures and assignment, (Monitor student’s activities.) All this can be solved by the development of this learning platform.

Online learning creates flexibility by eliminating the need for learning to happen at a set time and a set place. Mobile takes learning flexibility even further by making instructional content such as videos, podcasts, and other multimedia formats available on smartphones and tablets. What’s more learners have the added flexibility of being able to access this content on their mobile devices whenever and wherever they want.

1.0.1 Statement of WorkThis effort includes the following:
Define the needed functions.

Further define the critical functions and requirements.

Form a project team.

Create and approve a project charter
Create and approve a project plan for the product development
Implement a test bed focusing on high priority functions
Test functionality and assess strengths and deficiencies of the product and implementation methods
Make recommendations and project plan for a full production, including
Roles and responsibilities
Functions to include
Implementation methods
Timeline
Report findings
1.0.2 ObjectivesUsing the mobile phone as a learning platform can help create a sustained, supportive learning environment even beyond the classroom.

The platform should be able to:-
Improve completion and retention rates.

Provide for learning flexibility.

Allow for collaborative learning i.e. shared calendars and access to forums.

Enable learners to perform tasks on time and interactively.

Better performance.

Get feedback/compliments on assignments.

1.0.3 ConstraintsThe following limitations and constraint have been identified for this project:-
Connectivity problems when it comes to uploading and downloading of information because of poor or absent mobile network signals.

Limited information due to the mobile screen size and resolution
Device compatibility with the type of content
1.0.4 AssumptionsThe following assumptions were made when developing this statement of work:-
JKUAT will continue to support staff involvement with this project.

More specific staff commitment levels will be defined in the project plan.

The Charter was approved on ……..

2.0 Scope Overview2.0.1 Work Breakdown StructureFigure 2.0.1 Work breakdown
1885950257810Mobile learning platform
00Mobile learning platform

274320072390
4895850711206762757112067627461595
1905024765Course Content
00Course Content
441960034290Test and Deployment
0Test and Deployment
226695091440Application Programming
0Application Programming

4905375262890600075205740
57150001943104533900203835453390020383534099502609852266950241935282892557150104775213360103822522288594615213360
4219575110490Quality Testing
0Quality Testing
517207581915Deployment
00Deployment
2876550167640Integration
00Integration
1885950167640App Design
00App Design
228600095250-304800110490Course Design
0Course Design
647700110490Course Authoring
0Course Authoring

2.0.2 Business scopePhase 1 – Requirements
Define and prioritize preliminary list of functions
Assess user needs and modify functions and priorities if appropriate
Create online survey
Advertise on existing data discovery sites and newsletter
Compile results and compare to functions list and modify as appropriate.

Assess mobile service requirements.

Clarify what comprises comprehensive documentation of mobile service
Agree on a list of key characteristics that must be addressed to achieve trust in mobile service.

Phase 2 – Implementation
Identify training needs of implementation group
Research functionality and configuration options
Develop a plan for which product functions will be implemented
Develop a configuration plan
Install and configure software
Implement client functions and complete design work
Develop a test plan and test cases
Test implemented functions
Assess how implemented functions meet the defined needs
Describe what other functionality is needed
Recommend how that functionality might be acquired or created
Phase 3- Make Recommendations and Plan for Production
Make recommendation for a production
Functions to include
Implementation strategy
Roles and responsibilities
Estimated up front and ongoing costs
Benefits and Risks
Mobile service level agreements
Develop a template for a service level agreements
Report to the stakeholder’s on progress.

2.0.2 Scope Management Plan Proposed scope changes will be assessed in terms of impact to project schedule and cost. Any changes to this scope must be documented in a revised version of the project plan. Approval of Project Manager is required. Any scope changes involving staffing changes also require the approval of the project owners.

3.0 Budget OverviewEstimated budget for the project:-
All staff time, hardware, software and other resources will be contributed in-kind from participating organization. A request will be made to JKUAT to allow for staff interruption during working hours for some key project tasks.

3.0.1 Budget Management
Any changes to the budget must be documented in a revised project plan. Approval of Project Manager and Project Owners is required.

4.0 Project TeamThe following people and organization are stakeholders in this project and included in the project planning. Additional project team members will be added as needed.

Project Owners: Ensure adequate resources are available and track project status.

JKUAT Nairobi center
Project Manager: Lead the planning and execution of the project.

Pondi Brian
Project team members: Plan and design the product and advice on implementation.

Joan Tarus
Andrew Kyalo
Ruth Omayo
Implementation Team: Implement test bed version of the product.

Pondi Brian
Joan Tarus
Andrew Kyalo
Ruth Omayo
Survey Team: Plan and implement a user survey.

Andrew Kyalo
Ruth Omayo
Service Requirement Team: Identify issues related to Mobile service requirement and how they might be implemented.

Pondi Brian
Joan Tarus
4.1 Project Team Management
The project manager coordinates the project tasks assigned to team members. Changes to the project team require approval of the Project Manager for the affected areas if relevant. Changes will be tracked in revisions to the project plan.

5.0 Project ScheduleKey project tasks, responsible team members and estimate hours:
Detailed project schedule is provided below.

5.0.1 Schedule ManagementThe project Schedule will be posted online and updated as tasks are completed. Any changes to the schedule must be documented in a revised project schedule.
Table 5.0.2 Project Functions and Activities: Functions/Activity Description Date
Project initialization Initial review of the project and planning of specifications 1 March 2018
Project report Report progress to stakeholders 4 March 2018
Project planning meeting Discuss goals, objectives, and issues 6 March 2018
Operations Concept Document Present operational concept documentation 6 March 2018
Progress report Report progress to stakeholders 7 March 2018
Operational concept signoff Management verifies meeting standards 9 March 2018
Project planning meeting Discuss goals, objectives, and issues 10 March 2018
Question responses Deliver answers to stakeholders questions 12 March 2018
Project report Report progress to stakeholders 14 March 2018
SPMP Draft Deliver draft version of project management plan 16 March 2018
Project planning meeting Discuss goals, objectives, and issues 17 March 2018
SPMP final Present final-version of SPMP to the stakeholder 19 March 2018
Progress report Report progress to stakeholders 21 March 2018
SPMP signoff Management verifies SPMP meets standards 23 March 2018
Project planning meeting Discuss goals, objectives, and issues 23 March 2018
Question responses Deliver answers to stakeholders questions 26 March 2018
Requirement specification draft Draft preliminary version of requirement specification. 30 March 2018
Program design Begin initial design of the application 30 March 2018
Project planning meeting Discuss goals, objectives, and issues 30 March 2018
Requirement specification final Present final version of requirement specification to stakeholders 1 April 2018
Progress report Report progress to stakeholders 4 April 2018
Requirement specification signoff Stakeholders verify requirement specification meets standards 6 April 2018
Application design document draft Begin functional design development for programming representation of data 6 April 2018
Project planning meeting Discuss goals, objectives, and issues 7 April 2018
Application design documentation final Present final version of design documentation to stakeholders 9 April 2018
Progress report Report progress to stakeholders 11 April 2018
Application design documentation signoff Stakeholders verifies design document meets standards 13 April 2018
Application design documentation draft Design functional development programming representation of data 13 April 2018
Project planning meeting Discuss goals, objectives, and issues 14 April 2018
Question responses Deliver answers to stakeholders questions 16 April 2018
Progress report Report progress to stakeholders 18 April 2018
Application design documentation final Present final version of design document 20 April 2018
Software testing manual draft Draft preliminary version of the application testing manual 20 April 2018
Project planning meeting Discuss goals, objectives, and issues 21 April 2018
Progress report Report progress to stakeholders 25 April 2018
Application design documentation signoff Stakeholders verifies design document meets standards 27 April 2018
Project planning meeting Discuss goals, objectives, and issues 28 April 2018
Application testing manual final Present final version of testing manual to stakeholders 30 April 2018
Application user’s manual draft Draft preliminary version of user’s manual 30 April 2018
Question responses Deliver answers to stakeholders questions 30 April 2018
Progress report Report progress to stakeholders 1 may 2018
Software testing manual signoff Stakeholders verifies testing manual meet standards 3 may 2018
Application user’s manual final Present final version of user’s manual to stakeholders 3 may 2018
Project planning meeting Discuss goals, objectives, and issues 4 may 2018
Proof-of-concept Mobile learning application Demonstrate a working prototype based on specification 6 may 2018
Test report draft Draft preliminary version of test report 6 may 2018
Progress report Report progress to stakeholders 8 may 2018
Application user’s manual signoff Stakeholders verifies user’s manual meets standards 10 may 2018
Project planning meeting Discuss goals, objectives, and issues 11 may 2018
Test report Final Present test results to stakeholders 13 may 2018
Question responses Deliver answers to stakeholders questions 13 may 2018
Progress report Report progress to stakeholders 15 may 2018
Project planning meeting Discuss goals, objectives, and issues 18 may 2018
Test report signoff Stakeholders verifies test report meets standards 20 may 2018
Project planning meeting Discuss goals, objectives, and issues 25 may 2018
Formal project presentation Formally present the product to stakeholders 27may 2018
Product prototype Deliver product prototype to stakeholders 28 may 2018
Table 5.0.3 Gantt chart
Functions/Activity March April   May
Weeks
1 2 3 4 5 6 7 8 9 10 11 12 13
Project initialization                          
Project report                          
Project planning meeting                          
Operations Concept Document                          
Progress report                          
Operational concept signoff                          
Project planning meeting                          
Question responses                          
Project report                          
SPMP Draft                          
Project planning meeting                          
SPMP final                          
Progress report                          
SPMP signoff                          
Project planning meeting                          
Question responses                          
Requirement specification draft                          
Program design                          
Project planning meeting                          
Requirement specification final                          
Progress report                          
Requirement specification signoff                          
Application design document draft                          
Project planning meeting                          
Application design documentation final                          
Progress report                          
Application design documentation signoff                          
Application design documentation draft                          
Project planning meeting                          
Question responses                          
Progress report                          
Application design documentation final                          
Software testing manual draft                          
Project planning meeting                          
Progress report                          
Application design documentation signoff                          
Project planning meeting                          
Application testing manual final                          
Application user’s manual draft                          
Question responses                          
Progress report                          
Software testing manual signoff                          
Application user’s manual final                          
Project planning meeting                          
Proof-of-concept Mobile learning application                          
Test report draft                          
Progress report                          
Application user’s manual signoff                          
Project planning meeting                          
Test report Final                          
Question responses                          
Progress report                          
Project planning meeting                          
Test report signoff                          
Project planning meeting                          
Formal project presentation                          
Product prototype                          
6.0 Communication PlanThe project team will maintain a schedule of meetings. All members, project owners and others who have expressed interest are included in the list for meeting agendas and meeting notes. If a particular meeting is not needed, it will be cancelled. The members us Google Doc for collaborative work. This work is accessible only to authorized users. Additional or alternate team members collaborative work sites will be considered if the need arises.

The stakeholders will be kept up to date of the progress of the project through their representatives.

Individual task teams will work closely on a weekly or daily basis while completing specific tasks.

7.0 Risk Management
As issues arise within the project, the team members will determine if the issue is significant enough to report it to the Project Manager. The Project Manager, in consultation with the Team, will decide if the issue should be reported to the full project participants. If so, the collaborative site will be used as a place to describe and track issues. For project team members to continue efficiently, it is desirable that most issues be resolved within the team or with consultation with the Project Manager. Issues may include testing results, unexpected problems, and other items that impact project completion.

8.0 Monitoring and Controlling PlanProject monitoring will be done in all meetings and approved by the Project Manager. The major monitoring mechanism is the testing phase of the project. Suggestions with regards to documentation can be made by team members and the stakeholders and shall be approved by the Project Manager
9.0 Project Plan Documents SummaryAll significant electronic project documentation will be posted on the collaborative site. Team members will determine when a document is sufficiently complete to post on the site.

10.0 ApprovalBelow is documentation of confirmation that project owners and project manager have reviewed the information contained in this document and approve of this as the formal project plan for the JKUAT Nairobi Mobile learning platform.

Table 10.0.1 Project approvalsTitle Name Signature Date
Client Representative Customer Representative Project Manager Software Lead Development Software Quality Control The Project Plan will be approved by the Project Owners and Project Manager. Project Changes will be approved by the Project Owners and Project Manager too.

x

Hi!
I'm Loren!

Would you like to get a custom essay? How about receiving a customized one?

Check it out