· Web viewThe client can use the application to request for clean the clothes, laundry bag...
Transcript of · Web viewThe client can use the application to request for clean the clothes, laundry bag...
pert
PROJECT PLANCLEAN4U09, OCT,2018
Submitted By:
Sara Almarzooqi – H00232243Rehab Mohammed – H00247060
Najla Alzaabi – H00154381Fatima Khadem – H00236617
Supervised By:
Submitted By:
Sara Almarzooqi – H00232243Rehab Mohammed – H00247060
Najla Alzaabi – H00154381Fatima Khadem – H00236617
Supervised By:
Anand Pandiyan
Project plan 1
Higher Colleges of Technology Abu Dhabi Women’s College Computer and Information Science
Table of ContentsClient Requirements....................................................................................................3Constraints:......................................................................................................................4Scope Statement:...........................................................................................................5Work breakdown Structure “WBS”:.....................................................................7
WBS Dictionary.......................................................................................................................9Time Management:.....................................................................................................14Estimation of Duration.............................................................................................15
Project Tasks Lists from MS Project..................................................................16Project Milestone Tasks...........................................................................................16Cost Management:......................................................................................................18Risk Management:......................................................................................................19References:.....................................................................................................................22
Project plan 2
CLIENT REQUIREMENTS
STAKEHOLDERS:
The client of the Application is for old people, handicapped (can’t walk) and busy people whose
cant clean their clothes by themselves also it will help those people, and some people they don’t
know how to clean specific type of fabrics. which makes them the main stakeholders of the
project in which by their use of the application it helps to live their life easier. Considering the
application is going to affect those people and their lifestyle. Also, the program will help those
people, and this makes secondary stakeholders. Another primary stakeholder is us as a team
since we are responsible for designing and programming the application in a way to be effective
for the target users which is a laundry bag.
Project Requirements:
The client can use the application to request for clean the clothes, laundry bag provides several
features for the client and easy communication for both partners. The application can get a
mobile notification when the laundry basket is full by a sensor, which will help them to see how
many times they clean and how much its cost. Also, there is two option for paying the bill cash
or credit card and there is an option to pay daily, weekly and monthly. Mobile system work on
Android and iOS operating system and it will save the user data and info, the application will
Project plan 3
help users to manage the time, Schedule pick-ups at desired time Automated pick-up scheduling
based and view laundry bag status, Track garment.
CONSTRAINTS:
Constraint the project is a restriction that defines a project's limitations; the scope, cost, time. The constraint divided to Internal/ External, Mandatory/ Optional, Present/Futureas following:
Constraint description Internal/External
Mandatory/ Optional
Present/Future
The application should be available in 24 hours
Internal Optional Future
The application must save the user data and info
Internal Mandatory Present
The application should have interactive elements.
Internal Mandatory Present
The project should commit to be finalized by 13.12.2018
Internal Mandatory Present
The project constrained by a budget of 36584 AED
Internal Mandatory Present
Project plan 4
SCOPE STATEMENT:
Outcome Scope Description
The study will focus on, the new laundry basket, which will provide mobile application for the clients of the laundry to request and clean for their own clothes, online and providing more features without coming all way down to the laundry shop.
This new basket will not only help the clients also, the laundry shop will achieve loads more benefits of our new laundry basket. Additionally, support the operating system for the laundry shop by making it tranquil and faster to communicate with the delivery person and clients. We have well defined the exact limitations, or level, of our project.
The Clean4U Application must be able to work on all mobile systems and run both Android and Apple's iOS mobile operating systems, naive designed, with earnest colors as the main Clean4U application, well-defined, easy to use and easy to memorize. The application will include five main tasks:
The ability to check laundry basket.
The ability to update the basket statues.
The ability to talk and communicate with customers from anywhere outside the country.
The ability to pay online if any payment is pending.
The ability to choose desire time for pickups and delivery.
Product Acceptance Criteria
Application works well without bugs or errors. Each activity is well-defined and organized. All recorded and updated data are secure into cloud database.
Project plan 5
Project & product related deliverables
Project management-related deliverables:
Project proposal, literature review, group agreement, scope statement, work break down structure WBS, schedule, cost baseline, status details, final project report, application implementation, testing, lessons-learned report.
Product-related deliverables:
Analysis report, designing documents, software code, and most importantly, an effective laundry application and basket with a sensor.
Project exclusions
A laundry application outcome that benefits to make serval thing. A prototype for the laundry application and basket. The laundry application allows one time to register with the same email.
Project assumptions
We assume the project plan will be agreed by the laundry store within 5 days.
We assume the laundry application will be used just by customers, business owners.
We assume that the laundry basket will be updated every day. We assume the sensor will be available for the project within 7 days.
Project plan 6
WORK BREAKDOWN STRUCTURE “WBS”:
Work breakdown structure
Element Number
WBS ElementsActivity, Task, or Sub-Task
A Clean4U ApplicationA.1 Initiating
A.1.1 Select project managerA.1.2 Form project teamA.1.3 Identify stakeholderA.1.4 Develop project proposalA.1.5 Initiation complete
A.2 PlanningA.2.1 Collect requirements
A.2.1.1 Hardware requirementsA.2.1.2 Product requirements
A.2.2 Develop scope statementA.2.3 Create WBSA.2.4 Planning complete
A.3 ExecutingA.3.1 Database design
A.3.1.1 Laundry servicesA.3.1.2 Laundry locationsA.3.1.3 Laundry descriptionA.3.1.4 Clothes statuesA.3.1.5 Delivery service
A.3.2 Database design completeA.3.3 Application design
Project plan 7
A.3.3.1 Design sketchesA.3.3.2 Pages templates
A.3.3.2.1 Registration pageA.3.3.2.2 Clients information pageA.3.3.2.3 Main Laundry pageA.3.3.2.4 Bag pageA.3.3.2.5 Payment page
A.3.4 Application design completeA.3.5 Application construction
A.3.5.1 ControlsA.3.5.2 FunctionsA.3.5.3 Feedback
A.3.6 Application construction completeA.3.7 Application testing
A.4 Monitor and controllingA.5 Closing
A.5.1 The project is submitted
Project plan 8
WBS Dictionary
WORK BREAKDOWN STRUCTURE DICTIONARYProject title: Clean4U ApplicationWBS item number: 1.3WBS item name: Identify stakeholders
Task description:Making a list of stakeholders of the project and their requirements. Such as; project manager, team members, project sponsors, customers and anyone related to the project. This will be done by meetings.
Acceptance criteria:Stakeholders has to approve and sign the requirements.
Deliverable(s):Stakeholder registerProject and product requirements
Resources assigned:
Duration:3 days approximately
Cost:0 DHS
Dependencies after (Successor)Develop project proposal and literature review
Dependencies before (Predecessor)Form project team
Due date: Approved: project manager
Project plan 9
WORK BREAKDOWN STRUCTURE DICTIONARYProject title: Clean4U ApplicationWBS item number: 2.1WBS item name: Collect requirements
Task description:Collect project and product requirements from stakeholders and store customer. This will be done partly in identifying stakeholders’ task and partly in questionnaire form for laundry store clients.
Acceptance criteria:Requirements gathering should cover all stakeholders of the project.
Deliverable(s):List of project and product requirements.
Resources assigned:Project proposal approval.
Duration:4 days approximately
Cost:50 DHS
Dependencies after (Successor)Hardware requirements
Dependencies before (Predecessor)Project charter
Due date: Approved: project manager
Project plan 10
WORK BREAKDOWN STRUCTURE DICTIONARYProject title: Clean4U ApplicationWBS item number: 3.1WBS item name: Database design
Task description:Create and design the database for the store with its full information and data, create the entities, attributes and the relationships to move data from one entity to another and let rental process be consistence.
Acceptance criteria:All data of the store has to be in the cloud database.The data has to be consistence with the available services in the laundry store.
Deliverable(s):Database of the Laundry store
Resources assigned:Project proposalScope statement
Duration:2 weeks approximately
Cost:2 weeks = 10 working days4 hrs. / day5 DHS / hr.4 * 10 * 5 = 200 DHS
Dependencies after (Successor)Design sketches
Dependencies before (Predecessor)WBS
Due date: Approved: project manager
Project plan 11
WORK BREAKDOWN STRUCTURE DICTIONARYProject title: Clean4U ApplicationWBS item number: 3.3.2WBS item name: Pages templates
Task description:Submit templates of the Clean4U Application which include colored design and pictures with its functions and the data flow for all app views.
Acceptance criteria:Pages of the application has to be consistence, visible, easy to use and simple.Applications template should have easy simple navigation bar.
Deliverable(s):Application interface design
Resources assigned:Project proposal approvalScope statement approvalDatabase design approval
Duration:7 days approximately
Cost:6 hrs. / day20 DHS / hr.6 * 20= 120 DHS
Dependencies after (Successor)Applications views
Dependencies before (Predecessor)Design sketches
Due date: Approved: project manager
Project plan 12
WORK BREAKDOWN STRUCTURE DICTIONARYProject title: Clean4U ApplicationWBS item number: 3.5.3WBS item name: Feedback
Task description:Code function within the application to give the user feedback for processes, errors or missing information. The feedback could be by text message to the user phone number or alert box inside the application.
Acceptance criteria:Feedback should be clear to users to know what is happening while they are using the app.
Deliverable(s):Application with clear feedback
Resources assigned:Project proposal approvalScope statement approvalDatabase design approvalApplication design approval
Duration:2 days approximately
Cost:0AED
Dependencies after (Successor)Application testing
Dependencies before (Predecessor)Functions
Due date: Approved: project manager
Project plan 13
TIME MANAGEMENT:
Network Diagram:
For better view, please check the MS project.
Project plan 14
Critical Path:
Task name Duration PredecessorsA. Design sketches 2 days -
B. Pages templates 1 day A
C. Registration page 1 day B
D. Clients information page 1 day C
E. Main Laundry page 1 day D
F. Bag page 1 day E
G. Payment page 1 day F
Path>> A+B+C+D+E+F+G= 8daysCritical path where float (late start – Early start) = 0Since the duration is one day from B activity till G activity there will be a critical path
Estimation of Duration
PERT CalculationPERT is a project network analysis technique used to estimate project duration when there is a high degree of uncertainty with the different activity duration estimates 3-point estimations an estimate that contains an optimistic, and pessimistic estimates.PERT weighted average formula = (O+4*M+P) /6
Task Name Optimistic
Most Likely
Pessimistic
Formula
Create WBS 3 4 3 (3+4*4+3) /6 = 3.7
Develop scope 3 4 2 (3+4*4+2) /6 = 8
Project plan 15
statementDevelop project charter
3 2 3 (3+4*2+3) /6 = 6.8
Project Tasks Lists from MS Project
Project Milestone Tasks
i. Gantt chart:
Project plan 16
i. Mark Project Milestones in detail:
Project plan 17
Major Milestones Expected Date
Initiating Phase completed 24/Sep/18
Planning Phase completed 3/Dec/18
Executing Phase completed 6/Nov/18
Application design completed
26/Nov/18
Application Construction completed
3/Dec/18
Monitoring and Controlling Phase completed
12/Dec/18
Closing completed 13/Dec/18
COST MANAGEMENT:
Estimating costs is an essential part for any project to be successful when is completed. In details, many resources are required to be carried out through the project such as hardware and software resources to help in producing the Service and app. We estimated our needs from the software and hardware by determining the resource's name and type, defining quantity with the price for each resource. Then find the total cost for each resource by multiplying quantity and price. After that, we sum all the costs to get the total cost of our project that is AED 36584. An additional cost is added to the total cost to reserve for any need during implementation. So, we estimated the cost is by browsing the internet and comparing between prices. The table below shows the total cost of the project:
For example, for Lan + fix the calculation is like:
3(months) * 299 (cost per month) + 150 (fix cost) = 1047 dhs
Project plan 18
Resources Type Quantity Price Cost (AED)Adobe Photoshop CC Software 1 74/mon 148MS program: Word 2010, Outlook 2011, Visio 2010, MS PowerPoint, MS Project 2010. Software 2 Free 0
XCode Version 9.4 Software 2 Free 0ORACLE SQL Developer Data Modeler 17.2 Software 2 Free 0
Star Uml Software 2 Free 0Prepo Software 1 Free 0Create website Software 1 Free 0Google Drive Software 1 Free 0Cloud service Software 1 Free 0
Laptop MacBook pro Hardware 2 6299 12598
LAN + fix Hardware 1 299/mon 1047
Labor cost 4 1700/mon 20400Raspberry pi 3 B+ Hardware 1 191 191Ultrasonic distance sensor Hardware 1 30 30Laundry basket Hardware 1 50 50Raspberry pi kit Hardware 1 120 120Tape Hardware 1 20 20Reserve - 2000
Total Cost 36584
for labor cost = 4 (programmers) * 1700 (cost per month) * 3(months) = 20400 dhs
RISK MANAGEMENT:
The risk response plan is based on selecting a strategy that is based on the following responses: Avoid, Transfer, Mitigate or Accept for each identified risk. Also, the description must be defined and be suitable to the significant risk with categories. The risk's category is either Technical, Project Management, External, or Organizational. In addition, in the risk response plan, the reasons of the risk that likely to be happening in a specified stage must be defined and discussed with the responsible member of the team project of that stage. However, qualitative risk analysis is different from a risk response plan as it shows the possible solutions for each risk in the project. Also, it identifies the probability and impact matrix tools and technique to measure the probability of each possible risk. The table below shows how the total scale is calculated:
Probability Impact Scores.05 LL
Impact Scores .20 L
Impact Scores .40 M Impact Scores .60 H Impact Scores .80 HH
0.8 0.04 0.16 0.32 0.48 0.64
0.6 0.03 0.12 0.24 0.36 0.48
0.4 0.02 0.08 0.16 0.24 0.32
0.2 0.01 0.04 0.08 0.12 0.16
The table below illustrates the findings in the updated Risk Register:
Project plan 19
LL=Low Low L= Low M=Medium H=High HH= High High= High Risk
= Medium Risk
= Low Risk
No. Risk Description Category RootCause
RiskOwner
Potential response
RiskResponse
Probability
Impact
Total score/
Statues
1 Software issues
Complexity of usage and Software errors.
Technical Software needs training or search for online solution.
Najla Save the work daily in the USB. Update the system with latest version. Make sure that to have XCode updated version.Follow steps for registration and installation.
Mitigate 0.6 0.60H 0.36
2 NetworkConnection
Failure of internet connection so we cannot use the online resources or complete the whole project specially collecting data from sensor and communication between team workers.
Technical or Organizational
Damage in network cables, network devices or not paid Etisalat bills or low signals.
Fatima Try to disconnect and connect again back to Wi-Fi or connect to other available Wi-Fi if it’s possible or hotspot. use a 4G LTE USB Modem Adapter from Etisalat. Contact ISP such as Etisalat or DU.
Mitigate or Transfer
0.8 0.80HH
0.64
3 Application Errors
-Facing difficulty in developing the app- Facing some issues with cloud service or database
Technical Lack experience of using XCode
Rehab - Do some debugging for the application to fix any error.- Search for the solution through the internet
Mitigate 0.6 0.60H 0.36
4 Time management
The estimated finish date was too early because Project requires
Project Management
-Poor planning schedule- Some members do not
Sara - Increase participants, and re-divide the amount of work as needed- Increase the work time if it's needed for some
Accept 0.6 0.60M 0.36
Project plan 20
more time to get it finished.
finish their part on time.
tasks
5 Hardware issue
Hardware not working or functioning properly, broken or damaged. Hardware poor performance.
Technical
Do not match the project's requirements. broke some parts of sensor and Raspberry pi
Fatima While working on the project, make sure to back up the work on external storage (USB drive)- Before starting the project, we repaired and maintained the laptops by getting help from TSD.Ask technician or search for how to deal with sensors and Raspberry pi
Avoid 0.4 0.80HH
0.32
6 Lack of knowledge
The members do not have much knowledge in order to accomplish the project.
Internal Lack of programming knowledge and not having much experience specially in sensor and other related things to it.
Najla - All the team members are required to learn new skills to complete the project before the implementation start.
Avoid 0.4 0.40M 0.16
7 Scope creep
The client adds more functionality to be implement in the product.
Project Manageme
nt
There is no control on the scope because project manager does not have the expertise to handle such situations.
Rehab - Spend more time undersetting what the clients want exactly from this project.- The Project manager makes sure that the scope is clearly defined.
Avoid 0.6 0.40M 0.24
8 Team Lack of Project Lower Sara Create group Mitigate 0.2 0.60H 0.12
Project plan 21
Communication
communication between team members, project manager and sponsor.
Management
team communication, and the personality of the project manager weak.
discussion using weekly meeting, WhatsApp and email to be close to team members so they can discussed different thing about the project.
REFERENCES:
Project Management Institute. (2013). A Guide to the Project Management Body of Knowledge. Pennsylvania: Project Management Institute.
Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Pennsylvania : Project Management Institute.
Project plan 22