Week 5 - Assignment - Closure Checklist and Lessons Learned
pptx
keyboard_arrow_up
School
Capella University *
*We aren’t endorsed by this school
Course
3000
Subject
Information Systems
Date
Dec 6, 2023
Type
pptx
Pages
7
Uploaded by ibal1984
Project Closure
and Lessons Learned
Ian Lloyd Balido
Agenda
Project Closure Checklist
Project Post-mortem
Lessons Learned
Agenda
2
11/10/2022
11/10/2022
Project Closure Checklist
3
Project
Closure
Checklist
Dee Dee's Pawn Star Shop Website
Project Name: Dee Dee's Pawn Star Shop Website
Project Manager: Ian Lloyd Balido
Project Sponsor: Dorothy Deal
Item
Owner
Target Date
Completion Date
Deliverables handover to the sponsor owner
PM
05/19/2023
04/27/2023
Deliverables accepted and signed by the sponsor
PM
04/27/2023
04/28/2023
Completion of final project status reports
PM
04/27/2023
05/01/2023
Completion of Financial Processes and reports
PM
05/05/2023
05/02/2023
Final project review
PM
04/27/2023
05/05/2023
Completion of staff performance evalutaions and reports
PM
05/09/2023
05/04/2023
All software and hardware disposal completed
TM1
05/09/2023
05/05/2023
Project files storage and given to sponsor completed
PM, TM1,
TM2, TM3
05/16/2023
05/12/2023
Announcement of project completion to PM team, Sponsor, Public
PM
05/19/2023
05/16/2023
Reviewed for Closeout:
Approved for Closeout:
_____________________
_____________________
Project Manager
Sponsor
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
4
Project
Post-
mortem
Project Post-mortem
11/10/2022
Project post-mortem is a very important step for the project
team to discuss how the project went from start to finish by
analyzing and learning what worked and what didn’t in the
duration of the project. This allows them to avoid making the
same mistakes on the future projects (Ciccarelli, n.d.).
I will conduct my post-mortem meeting as follows:
•
Ensure I have a direct and on track agenda. Explain the
meeting’s purpose and rules; check-in with the project team;
short recap of the project; celebrate project wins; open floor
discussion/feedback; and close meeting on good note
(Ciccarelli, n.d.).
•
I will do a quick check-in with the team on a personal level
and not directly to discuss about the project to ensure that
there is no tension and that the team is comfortable in
sharing their feedback. I will make sure the morale of the
team is positive (Ciccarelli, n.d.).
•
I will discuss all the project highlights because it is important
to give credit to all the positive things that happened in the
project so that team is ready for the important part which is
the feedback portion (Ciccarelli, n.d.).
Project Post-mortem
5
Project
Post-
mortem
•
I will start easing slowly into the feedback portion by asking
questions such as:
1.
What contributed to the project’s success?
2.
What do you think made the project ran smoothly?
3.
What parts of the project ran smoothly?
4.
What do you think the client feel about how the project went? You think we meet
or exceed their expectation? (Ciccarelli, n.d.)
•
I will start the feedback portion by making it clear that the rules
of the meeting is no blaming; provide specific and actionable
feedback; one speaker at a time; and no arguing (Ciccarelli, n.d.).
•
I will listen to feedbacks from the entire team and will ask a few
questions like:
1.
Were there any issues that need to be addressed
2.
What are some improvement we can implement on the flow the next time?
3.
Do you feel we had support and tools to handle the project?
4.
What do you suggest the team leaders could do better next time?
5.
Did you team leaders provide you with everything you needed to successfully
complete this project? (Ciccarelli, n.d.)
•
Lastly, I will close the meeting on a positive note and have the
entire team feel confident that the project was successful
regardless of any issues we faced (Ciccarelli, n.d.).
11/10/2022
6
Lessons
Learned
Lessons Learned
11/10/2022
Lessons learned from this project are as follows:
1.
It is better to have multiple software and hardware product options
to make sure the right product for the website is picked.
2.
It is better do a thorough research of multiple web hosting services
before committing to ensure that the website has features and
enough storage to work properly.
3.
It is better to have multiple web design options to present to the
sponsor to ensure that we are capturing what the sponsor envisions
their website to look like.
4.
It is important to check compatibility of all software, hardware, and
web hosting services to ensure the web design and functionality is
as expected.
5.
Make sure to thoroughly inspect and check for website functionality
before deploying to public to ensure there are no negative reviews.
6.
Always monitor the website after opening to public to ensure speed
and functionality continually works.
7.
Project Team constant communication throughout the project is vital
to ensure the project runs smoothly.
8.
It is important to always address negative issues before it gets
bigger.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
7
Resources
Resources
11/10/2022
Kloppenborg, T. J., Anantatmula, V., & Wells, K. N. (2023).
Contemporary project management (5th ed.). Cengage
Learning.
Ciccarelli, D. (n.d.).
The Ultimate Guide to Hosting a Project Post-
Mortem That Doesn't Waste Time
. Retrieved from
https://www.goskills.com/Project-
Management/Resources/Project- post-mortem
Castle, K. (2019).
Lesson’s Learned Questions
. Retrieved from
https://www.projectcubicle.com/lessons-learned-template-
questions/#:~:text=Lessons%20Learned%20Example%20Questio ns
%201%20What%20was%20learned,Were%20the%20project%2
0milestones%20met%3F%20If%20not%2C%20why%3F