IT Project Estimates and Tracking help! how i can start off this project. assumi
ID: 3812990 • Letter: I
Question
IT Project Estimates and Tracking help! how i can start off this project. assuming i am the PM Manager and lets see i am implementing a new techinical ticketing system to record pc issues. we have to provide 2 estimates: bottom-up and top-down
Description
This section describes the objective of the lab based on your understanding from the actual lab. work.
Procedure and Notes
This section is an itemized list of notes you took by following the lab procedure.
It should cover any data/information that you are asked to note or observe at that procedure.
You can list any problems you encountered during the lab. Try to discuss why it occurred and how to get it right for the correct response, if you did.
Results and Reports
This section is for you to discuss your final results and/or report from your conclusion. If there are any files prepared as the results of the lab, make sure they are accessible electronically.
Reference and Acknowledgement
With or without encountering any difficulty, if you surfed the Internet to find some hints or to learn new information and/or technology to help you conducting the lab, you should include the information sources, such as the URLs, citations, or books.
If you received assistance from anyone (e.g. working together with some friend for the lab), you should acknowledge people’s contribution.
Explanation / Answer
Techinical ticketing system to record pc issues
What are the Tickets:
Top-Down Approach:
Take the tickets as a a whole.De.fine the priority of the ticket
Further categorize it into variors PC related issues.
Based on Issue Type it will be further categorized and assigned to the speacialized person of the team who will be the owner of the ticket and will be accontable.
In the top down approach chances are that the minute details get missed without a review by tester/QA team
Bottom Up Approach:
In Bottom up approach ticket will immediately be assigned to the team members who will be ticket owner. Their will be a deadline to complete the ticket and send it to further review by QA team who will then send it for User Acceptance Testing and finally the ticket will be closed after resolution. Here the ticket can be complete monitored.
Time for the Ticket:
Top-Down Approach:
Managers plan out the budget portfolio and other feasible checks. Many assumptions are made initially lacking accuracies. Planning the resources required and other decisions on cost and timelines. In this approach it is more of assumptions things are not precised. In this approach cost wont be an issues because managers will be planning out so budget can be done quickly and according resources are planned.
Bottom Up Approach:
This process is very lengthy as the planning is done by project team - they can make the accurate estimates with every minute details. This is helpful for a in depth budget resource and monthly/weekly reports.
To Start Off the project
1. List down the cost of the project and your budget estimations.
2. List down all the PC related issues that can be encountered. categorize it into various sections. Also,list one section as miscellaneous for unreported out of the box problems.
3. Estimate the resources required
4. Work on your timelines for resolving tickets under different sections.
5. Also, plan out your strategy in case an exception arises.
6. Prepare Fortnight/monthly status to be send to Leadership.
A mix of both Top Down and Bottom Up will be the best approach for technical ticketing system to record PC issues.
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.