Planning should be adapted to the nature of a project. The lessons learned document is a part of the project manager?s artifacts for the project. This docu

PM/310 v2

Status Report 3

PM/310 v2

Page 2 of 2

Status Report 3

Project name: Web Application Project

Company: Next Day Solutions

Project manager: Flavia Howard

Date: 5/26/20XX

Project week: Week 10

Project Status Overview

The project is nearing completion with most functionalities implemented. Final testing is underway, and only minor bug fixes remain. However, a budget overrun and final stakeholder feedback have posed additional challenges.

Completed

· Full feature implementation, including filtering functionalities

· Subscription module

· Finalized admin dashboard

Challenges

· Budget overrun due to extended development work

· Late-stage stakeholder feedback requiring last-minute UI adjustments

Overall Health

Green (on track): Despite challenges, all core deliverables are complete.

Open Issues

· Late-stage UI adjustments requested by stakeholders

· Impact: Requires minor rework before deployment

· Resolution: Adjustments made within final sprint time frame

· Budget overrun

· Impact: Exceeded by 15% due to additional development work

· Resolution: Absorbed through discarding low-priority work items

Deliverables and Milestones

· Completed: All core functionalities and integrations

· Pending: Minor UI tweaks and final testing

Key Performance Indicators (KPIs)

· Sprint velocity: 95% completion rate for final sprint

· Budget adherence: 15% over budget

· Issue resolution time: 2–3 days (improved from previous weeks)

· Feature completion rate: 98% for final sprint

Conclusion: Regular stakeholder check-ins are necessary to prevent rework.

Adapted with Permission from MyEducator. Copyright 2025 by University of Phoenix. All rights reserved.

Adapted with Permission from MyEducator. Copyright 2025 by University of Phoenix. All rights reserved.

image1.png

,

PM/310 v2

Project Charter

PM/310 v2

Page 2 of 2

Project Charter

Project name: Web Application Project

Company name: Next Day Solutions

Date: 3/12/20XX

This charter formally authorizes the Web Application Project to develop and implement a new Web Application for use in Next Day Solutions Company. A project plan will be created and submitted to the project sponsor, Micah Jones, marketing director, to assign all resources.

Project Objective

The purpose of the Web Application Project is to develop a professional and visually appealing website for the company, ensuring an excellent user experience. The web app will effectively showcase the company’s services, values, and expertise while providing an intuitive and engaging platform for visitors. This document aims to state all the requirements to fulfill. This project meets Next Day Solutions’ need to establish a strong online presence.

Project Scope

Design

Within the scope of this project, the design of the following interfaces will be performed:

· Website landing page (no iteration limit)

· Login, Signup, Forgot Password, and Terms & Privacy pages

· Admin dashboard page

· Admin profile page

· Admin service page

· Admin settings page

Web Interface

Within the scope of this project, the following interfaces and features will be developed:

· One-page responsive landing page according to the agreed-upon design

· Functionality of Login, Signup, and Forgot Password pages

· Admin dashboard that has the following features and components:

· Dashboard overview

· User management

· Web app configuration

· Admin profile page that enables users to:

· Manage their profile photo

· Update their “Name”

· Update their “Email”

Integration with Third-Party Applications

The application will be integrated with the following platforms:

· Google Analytics

· HubSpot

Out of Scope

· It is anticipated but out of scope to add a blog in the application.

· It is anticipated but out of scope to implement a multi-language feature.

Project Deliverables

The project deliverables will include the following:

· Meetings and discussion notes with project stakeholders

· Technical analysis and application workflow

· Mockups and design sources

· Quality assurance documentation, including test cases and their results

· Deployment note(s)

· Access to the application infrastructure, including the database and the source code

· A hosted solution as specified in the scope

Project Manager

The project manager, Flavia Howard, is hereby authorized to interface with management as required, negotiate for resources, delegate responsibilities within the framework of the project, and communicate with all contractors and management, as required, to ensure the successful and timely completion of the project. The project manager is responsible for monitoring the schedule, cost, and scope of the project during implementation and maintaining control over the project by measuring performance and taking corrective action.

Milestone Schedule

The project plan will be implemented per the following milestone schedule. Upon approval of the project charter, resources will be assigned to the project, and work will begin within 5 business days.

The high-level milestone schedule is:

· Mar. 19, 20XX: Project plan complete and approved

· Apr. 2, 20XX: Requirement gathering, design, and validation completed

· Apr. 16, 20XX: Setup of the required environment and technical architecture completed

· May 28, 20XX: Development of the application with all features stated in the scope section completed

Steps	Project Item	Timeline
1	Project charter approval	—
2	Requirement gathering, design, and validation	2 weeks
3	Setup of the required environment and technical architecture	2 weeks
4	Development of the application with all features stated in the scope section	6 weeks

Project Budget

The budget for the Web Application Project is $28,000. The following table splits this cost according to the resources that will be assigned to the project:

Item	# of Resources	Hourly Rate	Duration	Total Cost
Designer	1	$50	80 hours	$4,000
Technical leader	1	$90	80 hours	$7,200
Full-stack developer	2	$70	240 hours	$16,800

Sponsor Acceptance

Approved by the project sponsor:

Micah Jones

Marketing Director

Date:

Adapted with permission from MyEducator. Copyright 2025 by University of Phoenix. All rights reserved.

Adapted with permission from MyEducator. Copyright 2025 by University of Phoenix. All rights reserved.

,

PM/310 v2

Lessons Learned Document

PM/310 v2

Page 2 of 2

Lessons Learned Document

Complete all sections. Remove the italicized instructional text prior to submitting.

Project name:

Project manager: Flavia Howard

Project Overview

Reflect on how the project objectives and scope were defined and refined throughout the project. Discuss how the team adapted planning to meet evolving requirements. This should be approximately 75–100 words.

What Went Well

Highlight successes, such as effective team collaboration, effective tools and techniques, Scrum practices that worked well, or milestones achieved efficiently. This should be approximately 75-100 words.

Challenges

Identify obstacles encountered during planning and execution (e.g., unclear requirements, team capacity issues, communication breakdowns, scope creep, resources, etc.). This should be approximately 75–100 words.

Key Lessons Learned

Reflect on what was learned throughout the Next Day Solutions project, including the challenges that occurred. What worked and should be repeated? What should be changed or avoided? What are the improvements for the future? Consider how agile practices like retrospectives could improve outcomes. This should be approximately 75–100 words.

Future Recommendations

List 3 recommendations for improvements of any of the following: process improvements, risk mitigation, resource allocation, timeline and scope management, tool or technology recommendations. This should be approximately 50–100 words.

Final Thoughts

Describe any forward-thinking suggestions for the future. This should be approximately 50–100 words.

Action Items

List 3 items that need to be improved prior to the next project, such as the communication plan, stakeholder engagement, etc. This should be approximately 50–100 words.

Appendix

List the documents that support any of these items. This should be approximately 10–30 words.

Copyright 2025 by University of Phoenix. All rights reserved.

Copyright 2025 by University of Phoenix. All rights reserved.

,

PM/310 v2

Status Report 2

PM/310 v2

Page 2 of 2

Status Report 2

Project name: Web Application Project

Company: Next Day Solutions

Project manager: Flavia Howard

Date: 5/3/20XX

Project week: Week 7

Project Status Overview

The project has made significant progress, with most core features developed. However, stakeholder engagement has emerged as a challenge, causing shifting requirements that have impacted development timelines.

Completed

· AWS integration

· Authentication and profile page

· Admin dashboard (basic functionality)

Challenges

· Changing stakeholder requirements for dashboard features, leading to rework

· Team conflict over resource allocation, slowing progress on dashboard enhancements

Overall Health

Yellow (minor issues) – Rework and team conflicts have delayed dashboard completion.

Open Issues

· Stakeholder engagement issues

· Impact: Continuous changes in dashboard requirements lead to rework

· Resolution: Weekly alignment meetings scheduled with stakeholders

· Team conflict over task prioritization

· Impact: Slower progress due to disagreements on feature priorities

· Resolution: Project manager facilitating discussions to resolve disputes

Open Risks

Delays in admin dashboard development

· Probability: Medium

· Impact: Could impact launch timeline if not resolved quickly

· Mitigation: Additional developer assigned to dashboard tasks

Deliverables and Milestones

· Completed: Authentication module, AWS integration, basic dashboard features

· Pending: Filtering features for the dashboard, email notifications, final testing

Key Performance Indicators (KPIs)

· Sprint velocity: 75% completion for Sprint 4 due to rework

· Budget adherence: 10% over budget due to additional development work

· Issue resolution time: 5–6 days (longer than target 2 days due to conflicts)

· Feature completion rate: 70% for Sprint 4

Conclusion: Regular stakeholder check-ins are necessary to prevent rework.

Adapted with Permission from MyEducator. Copyright 2025 by University of Phoenix. All rights reserved.

Adapted with Permission from MyEducator. Copyright 2025 by University of Phoenix. All rights reserved.

image1.png

,

PM/310 v2

Status Report 1

PM/310 v2

Page 2 of 2

Status Report 1

Project name: Web Application Project

Company: Next Day Solutions

Project manager: Flavia Howard

Date: 4/12/20XX

Project week: Week 4

Project Status Overview

The project is progressing well, with initial milestones completed on schedule. The mobile app design has been successfully wrapped up, and technical architecture setup is finalized. However, there are minor delays in the user interface (UI) design of the login/signup pages, which have caused minor backlogs in development.

Completed

· Requirement gathering and design validation

· UI for landing page, privacy policy, and terms of use

· AWS and GitHub environment setup

Challenges

· UI of login/signup pages delayed due to design dependencies.

· Google Analytics integration blocked due to UI issues.

Overall Health

Yellow (minor issues) – Delays in UI design impact development but are manageable with adjustments.

Open Issues

· Login/signup UI delays

· Impact: Blocking development of authentication modules

· Resolution: Prioritizing this in the next sprint with additional designer support

· Integration with Google Analytics blocked

· Impact: Affects tracking of visitor statistics

· Resolution: Technical leader working on resolving UI-related blockers

Open Risks

Resource Allocation Constraints

· Probability: Medium

· Impact: If UI delays persist, developers may need to be reassigned to other modules, slowing down progress.

Budget Overrun Due to Extra Design Hours

· Probability: Low

· Impact: Minor additional costs incurred for extra design support

· Mitigation: Monitoring closely and reallocating hours where needed

Deliverables and Milestones

· Completed: Requirement gathering, UI designs for landing page and legal pages

· Pending: Login/signup UI, AWS integration, admin dashboard UI

Key Performance Indicators (KPIs)

· Sprint velocity: 85% completion rate for Sprint 2

· Budget adherence: 5% over budget due to additional design work

· Issue resolution time: Average resolution time 3–4 days (slower than target 2 days)

· Feature completion rate: 80% for Sprint 2

Conclusion: Early UI design dependencies should be resolved before backend development begins.

Adapted with Permission from MyEducator. Copyright 2025 by University of Phoenix. All rights reserved.

Adapted with Permission from MyEducator. Copyright 2025 by University of Phoenix. All rights reserved.

image1.png

,