Coursework IT project

40

Coursework:IT project

MobileApplication Development for Barber Shop

This paper presents the Workbreakdown structure for development of online scheduler, a mobileapplication for barbershop. The main objective of the application isto allow clients schedule appointments with the barber, as well asallow the barbers plan appropriately based on the number of clientswaiting in a queue.

Below are the Work BreakdownStructure (WBS), Risk Analysis, Estimates of Efforts, Cost-BudgetEstimate, And Project Organization and Stakeholder Analysis.

WorkBreakdown Structure (WBS)

Outline

1

Initiate Project

1.1

Project Charter Development

Scope Definition

Establishment of requirements

Identification of High-Level Roles

Development of High-Level Budget

Identification of High-Level Control Strategies

Finalizing the Charter and seek Approvals

Consolidate the Project Charter

Meet to review the project charter

Make revisions to the project charter

Seek approval

2

Plan Project

2.1

Work plan development

WBS development

Formulate a Staffing Plan

Come up with a Project Schedule

Project budget estimation

2.2

Develop Project Control Plan

Communication plan development

Quality Management Plan development

2.3

Finalizing on Project Plan and seeking Approvals

3

Executing and Controlling the Project

3.1

Designing Framework

Defining the framework stages and activities

Designing the framework content

Designing the web framework

3.2

Building the Framework

Writing the content of the framework

Reviewing the quality of the content

Building the prototype of the web

3.3

Usability Testing

Web tool testing

Content Testing

Adjusting the framework based on feedback

3.4

Framework implementation

Moving the framework to the production environment

Announcing the availability of framework

4

Project closure

Post-Project Review

Celebrating the success

RiskAnalysis

  • Failure of the barber to be engaged in the process

    • This might result when the barber doesn`t get engaged with what is happening, and doesn`t allow us to ask him questions when we need to, then the application requirements might drift from the intent of the project which results in a product that doesn’t meet the barber’s needs. This will also allow us to guess things rather than know as facts. The risk is of medium probability, medium effect

    • To reduce this risk, we will set schedules ahead of time to book the barber on weekly bases. This allows us a medium in which to share knowledge and ask questions

  • Customers avoiding the app because it’s too cumbersome

    • This might result when the functionality requires the client to follow several step by step instructions before accessing the available barber, hence consuming more time. Also, some customers are anti-technology and may lack appropriate experience in dealing with mobile applications. This may limit their reception of the mobile app. They may, therefore, prefer visit the barber shop physically and do the booking to using the scheduler. The risk is high probability, high effect.

    • To reduce this risk, the development process will take into consideration user involvement from design, development, installation and use. The customers will be extensively involved during the testing process to help the application development team get critical feedback and identify any user experience problems.

  • Backend operation failing.

    • This might result if the mobile app fail due to hardware or software reasons. This will cause the app to fail which in turn stops all new scheduling. It might also cause the data to be lost which results in loss of the already scheduled appointments. The risk is of low probability and high volatility

    • To reduce this risk, we will use a cloud system as a backup, it mirrors our servers and would also be used for load balancing in case of increased demand that our servers can`t handle. Load balancing would allow the cloud backup to directly pick up all clients from current server in case of a failure.

Estimatesof Effort

Work Estimation Details

Effort Hours

Phases

Activity/Task

Optimistic

Most Likely

Pessimistic

Expected

Project Management

&nbsp

&nbsp

Develop project charter

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

Project Plan

3.0

2.0

0.4

1.80

&nbsp

Scope Statement

3.0

2.0

0.5

1.83

&nbsp

Schedule

3.0

2.0

0.7

1.90

&nbsp

Develop High-Level Budget

3.0

1.0

0.1

1.37

&nbsp

Define Effort

4.0

1.0

0.6

1.87

&nbsp

Finalize Charter and Gain Approvals

4.0

1.0

0.5

1.83

&nbsp

Hold Review Meeting

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

Revise Project charter

4.0

2.0

0.1

2.03

&nbsp

Gain approvals

5.0

1.0

0.2

2.07

Plan project

&nbsp

4.0

1.0

0.4

1.80

Develop Work Plan

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

Develop Work Breakdown Structure

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

Develop Project Staffing Plan

3.0

1.0

0.1

1.37

&nbsp

Develop Project Schedule

4.0

0.3

0.3

1.53

&nbsp

Develop Project Budget

3.0

0.7

1.0

1.57

Develop Project Control Plan

&nbsp

3.0

0.9

2.0

1.97

&nbsp

Develop Communication Plan

4.0

2.0

&nbsp

2.00

&nbsp

Develop Quality Management Plan

2.0

2.0

2.0

&nbsp

Finalize project Plan and Gain Approvals

&nbsp

3.0

1.0

0.3

1.43

&nbsp

&nbsp

4.0

1.0

1.0

2.00

Design Framework

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

Define framework stages and activities

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

Design framework content formats

3.0

1.0

0.1

1.37

&nbsp

Design web framework delivery tool

4.0

1.0

0.5

1.83

Build the Framework

&nbsp

4.0

1.0

1.0

2.00

&nbsp

Write the framework content

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

Review framework content for quality

3.0

1.0

0.1

1.37

&nbsp

Build web tool prototype

3.0

2.0

0.5

1.83

Test the Framework

&nbsp

4.0

1.0

0.5

1.83

&nbsp

Test usability of web tool

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

Test usability of content

3.0

1.0

1.0

1.67

&nbsp

Adjust framework based on user feedback

2.0

&nbsp

1.0

1.00

Implement Framework

&nbsp

2.0

1.0

1.0

1.33

&nbsp

Move framework to production environment

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

Announce availability of framework

3.0

1.0

2.0

2.00

Close the Project

&nbsp

1.0

&nbsp

1.0

0.67

&nbsp

Conduct Post-Project Review

2.0

1.0

1.0

1.33

&nbsp

Celebrate

2.0

1.0

2.0

1.67

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

&nbsp

Work Estimate Totals

&nbsp

98.00

34.90

24.60

48.33

Assumptions

  • It is assumed that all the members work part-time, at least 2hrs and at most 6hrs

  • Since the project is small, the project development will only have a maximum of 15 members

  • There are some tasks where the people responsible accord more time that the others. For instance, the implementation of the framework is likely to have 3 man-hours for movement of framework to production and 5 hours to announce the availability of the network.

Costbudget estimate

&nbsp

&nbsp

Rate $/Unit/Day

Quantity/ (unit/Day)

Total Cost ($)

S. No

Expenditures

&nbsp

1

Selection process

&nbsp

1.1

Staff Costs

&nbsp

1.1.1

IS department

100

4

400

1.1.2

Procurement department

100

4

400

1.1.3

User Department

100

2

200

1.2

Travel expenses

100

5

500

Sub total

&nbsp

&nbsp

1500

&nbsp

2

Software costs

&nbsp

2.1

Software User License

400

4

1600

2.2

Security Applications

300

2

600

2.3

Database user licences

200

1

200

Software Cost Sub total

&nbsp

&nbsp

2400

&nbsp

3

Hardware costs

&nbsp

3.1

Upgraded and dedicated servers

3000

2

6000

3.2

New Personal Computers

500

25

12500

3.3

UPS

300

5

1500

Hardware Cost Sub total

&nbsp

&nbsp

20000

&nbsp

4

Network costs

&nbsp

4.1

Cabling or wireless LAN, WAN or other network

300

1

300

4.2

Switching devices

400

5

2000

4.3

Routers

450

3

1350

4.4

Modems

30

10

300

4.5

lines Communications software

1000

1

1000

4.6

Leased or dedicated

700

3

2100

Network Cost Sub total

&nbsp

&nbsp

7050

&nbsp

5

Labour costs

&nbsp

&nbsp

5.1

Project team

&nbsp

5.1.1

Project manager

&nbsp

5.1.2

Project leader

300

1

300

5.1.3

Systems analysts

200

1

200

5.1.4

Programmers

200

2

400

5.1.5

Systems testers

200

1

200

5.1.6

Vendor consultants

200

1

200

Labour Cost Sub total

&nbsp

&nbsp

1300

&nbsp

5.2

User team

&nbsp

5.2.1

Team leader

100

1

100

5.2.2

Team members

100

2

200

5.2.3

Team managers

100

1

100

User team Sub total

&nbsp

&nbsp

400

&nbsp

5.3

Support costs

&nbsp

5.3.1

Client manager

100

1

100

5.3.2

IS support

100

1

100

5.3.3

DB analyst

100

1

100

5.3.4

Networking support

100

1

100

Support Cost Sub total

&nbsp

&nbsp

400

&nbsp

5.4

Office costs and project team

&nbsp

5.4.1

Office Accommodation (Temporary)

200

2

400

5.4.4

Project Management Tools (software)

500

2

1000

5.4.6

Administrative costs

200

30

6000

5.4.7

Communication support

50

30

1500

5.4.9

Printing e.g. user manuals and marketing materials

0.3

10000

3000

Office and Project Team cost Sub total

&nbsp

&nbsp

11900

&nbsp

6

Training

&nbsp

6.1

User training

500

10

5000

6.2

Temporary internal training facilities

100

2

200

6.3

Training the remaining users

500

20

10000

6.4

making and printing of training materials

100

10

1000

6.5

Travel expenses (during trainings)

150

25

3750

Training Sub total

&nbsp

&nbsp

19950

&nbsp

7

Data costs

&nbsp

7.1

Data clean-up

200

5

1000

7.2

Archiving of Data

200

5

1000

Data Cost Sub total

&nbsp

&nbsp

2000

&nbsp

8

Other costs

&nbsp

8.1

Internal Audit Reviews

400

5

2000

8.2

Project steering support

1000

10

10000

Subtotal for other Costs

&nbsp

&nbsp

12000

9

Overheads

&nbsp

9.1

Allocated business costs (others)

300

20

6000

Sub total

&nbsp

&nbsp

6000

&nbsp

10

Ongoing costs

&nbsp

&nbsp

10.1

Vendor Maintenance Charges

&nbsp

10.1.1.

– software

1400

3

4200

10.1.2

– hardware

100

2

200

10.1.3

– database

1000

1

1000

10.2

Internal Support

200

2

400

10.3

System back-up

1000

1

1000

Total ongoing costs

&nbsp

&nbsp

6800

&nbsp

Project cost calculations

&nbsp

&nbsp

Total project cost

&nbsp

&nbsp

91700

ProjectOrganization &amp Stakeholder Analysis:

OrganizationChart

ResponsibilityMatrix

DEVELOPMENT OF MOBILE APP

Project Sponsor

Project Manager

Project leader

System Analyst

Programmer

System Tester

vendor Consultant

Team Leader

Team members

Team Managers

Client Manager

IS Support

DB Analyst

Networking Support

1

Initiate Project

1.1

Project Charter Development

A

A

R

R

I

I

I

I

I

I

R

I

I

I

Scope Definition

Establishment of requirements

Identification of High-Level Roles

Development of High-Level Budget

Identification of High-Level Control Strategies

Finalizing the Charter and seek Approvals

Consolidate the Project Charter

Meet to review the project charter

Make revisions to the project charter

Seek approval

2

Plan Project

I

A

R

C

C

C

C

C

C

C

C

C

C

C

2.1

Work plan development

WBS development

Formulate a Staffing Plan

Come up with a Project Schedule

Project budget estimation

2.2

Develop Project Control Plan

Communication plan development

Quality Management Plan development

2.3

Finalizing on Project Plan and seeking Approvals

3

Executing and Controlling the Project

I

I

I

A

R

A

C

C

C

C

I

C

C

C

3.1

Designing Framework

Defining the framework stages and activities

Designing the framework content

Designing the web framework

3.2

Building the Framework

Writing the content of the framework

Reviewing the quality of the content

Building the prototype of the web

3.3

Usability Testing

Web tool testing

Content Testing

Adjusting the framework based on feedback

3.4

Framework implementation

Moving the framework to the production environment

Announcing the availability of framework

4

Project closure

I

R

A

C

C

C

C

I

I

I

I

I

I

I

Post-Project Review

Celebrating the success

Power

Power/Interest Grid

  • Programmer

  • Networking Support

  • DB Analyst

  • IS Support

  • System Analyst

  • Project Sponsor

  • Project Manager

  • Project Leader

  • Vendor Consultant

  • User Representatives (manager, leader, members)

  • System Testers

  • Training Manager

  • Legacy System Owners

Interest

Rolesof the key stakeholders

Theclient manager, user members, user leader and user manager willensure that the online scheduler is developed appropriately sincethey act as the main representatives of the clients who will bepaying for the service. Their main interest will be to ensure thatthe application developed meets the goals for functionality, scheduleand cost. They will be receiving status reports as stated in theproject charter.

Thevendor consultant represent the external parties who will be clientsfor the developed app. Mostly, the vendor consultants help duringlicensing and other support services as may be required during thedevelopment of the application.

Theproject sponsors, project managers and project leaders will ensurethat the project is developed as intended. They facilitate prioritizeand encourage the process.

Theprogrammers, system analyst, data base analysts and testers will beinvolved in the actual configuration, coding and testing theapplication.

Conclusion

Theproject development process entails various activities. Some of theactivities critical for the success of the project includedevelopment of work breakdown structure, estimation of the costbudget, estimation of the effort, establishment of the organizationalcharts and responsibility matrix, as well as the analysis of risks.Project sponsors, managers, leaders, data base analysts, networkingconsultant, tester, system analyst and user support will play a majorrole in developing the resources. The project budget is estimated at$91,700 and 15 employees.

Themain deliverable in this project are support documents (user manual,training and marketing documents) and the mobile application. Thebarber calendar and services will provide the types of data required.

Itis anticipated that after successful development of the application,users will be able to log-in once, select the service (time will beselected automatically), view the availability of the barbers, add anappointment, synchronize with the phone calendar and send an email tothe barber and the client.

Theonline scheduler project will therefore be an important asset, bothto the barber and the clients.