PM 490 Week 5 Program Reflection Example

What the Barn Taught Me About the Program: A Capstone Reflection on Project Management Learning and Next Steps

[Student Name]

University of Phoenix

PM/490: Project Management Capstone

Week 5 Assignment

[Instructor Name]

[Date]

The student voice, the cidery project and the career details are composites written for a model paper.

The capstone project for this program was the conversion of an 1880s dairy barn into a tasting room for Stone Lantern Cider Works, a composite family cidery in New York's Hudson Valley. Over four weeks I wrote its charter and plan, reported its progress and closed it. The tasting room opened two days early and slightly under budget, but the project did not go as planned: rotten sills, planning board conditions and a tight interior schedule tested most of what the program taught. This paper reflects on that experience and sets out how I will continue to develop.

Why Reflect

Crawford et al. (2006) argued that project management education should move beyond training technicians in tools toward developing reflective practitioners who can handle complex, ambiguous situations. Thomas and Mengel (2008) made a similar case, proposing that advanced project management education should prepare managers for complexity through experiential learning, reflection and attention to people. Reflection is how I turn one project's experience into judgment I can use on the next.

Lesson 1: Value Is Not the Building

In the principles course I learned that outputs, outcomes and benefits are different. Writing the barn charter, I first wrote objectives about finishing the renovation. I rewrote them as sales, events and margins, because the owners were not paying for a restored barn but for what it would earn. That shift changed later decisions: when the bar top upgrade was proposed, I asked whether visitors would notice and spend more, not only whether it was within budget.

Lesson 2: Authority Has to Be Written Down

The planning courses stressed governance and change thresholds. I put mine in the charter: $10,000 per change and half the contingency. When the sills turned out to be rotten, I approved what I could and took the rest to the owners the same day. Without written limits, I would have either waited for permission I did not need or spent money I had no right to spend.

Lesson 3: Bad News Early

The measurement course introduced research showing that status reports tend to favor good news. I agreed with the owners at the start that problems would go in the weekly update the week they appeared. That rule made the sill problem a one-day decision rather than a month of worry. It is the lesson I will carry most directly to my next job.

The most useful thing I wrote in the whole capstone was a one-line rule about reporting bad news.

Lesson 4: Tailor, Do Not Copy

From the agile course I learned to tailor. The barn was a predictive project, but the tasting room menu and layout of the bar were refined with the owners in short cycles using sketches and a cardboard mock-up. I did not force sprints onto construction, and I did not force a fixed plan onto decisions that benefited from trial.

Two Mistakes

First, I accepted three structural probes as enough. They missed most of the rot, and the project lost three weeks. I should have asked the engineer what the probes could not tell us and paid for more before pricing. Second, I treated neighbors as a permit risk rather than as stakeholders with real concerns about traffic and noise. Outreach came late, and the planning board's limit of 18 events reduced a key objective. I now think stakeholder engagement belongs in the first week of any project that affects a neighborhood.

What I Would Do Differently

If I managed the barn project again, I would change three things beyond the two mistakes above. I would build the schedule backward from the opening date in the first week, not the second, because the planning board's January hearing turned out to be the most important date in the whole project and I discovered that late. I would ask the owners to name one decision-maker for design choices; when both siblings had to agree on paint colors and bar materials, small decisions took a week. And I would keep a running cost forecast from the first day of construction rather than starting it after the first surprise, so that the owners always saw where the contingency stood.

Strengths and Gaps

Measured against the eight performance domains in the current standard (Project Management Institute [PMI], 2021), my strengths are planning, measurement and project work: I can build a schedule and baseline, report performance honestly and run a weekly rhythm with a contractor. My gaps are stakeholders, where I engaged too late; uncertainty, where I relied on too little information about hidden conditions; and team, since the capstone did not require me to lead a team over time.

How the Program Prepared Me

Looking back across the courses, the program's strongest contribution was vocabulary that lets me think precisely: outputs and benefits, baselines and forecasts, risks and issues, governance and management. Before the program I would have called every problem a risk and every document a plan. Its weakest area for me was practice with people outside the project team, such as neighbors and regulators, which the courses discussed but the assignments rarely required me to handle. The capstone exposed that gap, and the plan below addresses it.

Development Plan

Within three months: earn PMI's Certified Associate in Project Management, using the program's coursework toward its education requirement, to establish a recognized baseline.

Within one year: take a project coordinator role in a construction or facilities organization, where hidden-condition risk and neighbor relations are routine, and ask to own stakeholder engagement on at least one project.

Within three years: lead projects for long enough to meet the experience requirement for the Project Management Professional credential, checking the current requirements in PMI's handbook before applying.

Throughout: write a two-page post-project review after every project I work on, with lessons assigned to owners, as I did for the barn.

Conclusion

The capstone showed that the program's ideas work when they are applied to real decisions: value over outputs, written authority, early bad news and tailoring. It also exposed two habits to change, trusting thin information and engaging stakeholders late. The development plan addresses both gaps with certification, targeted experience and a habit of reflection that I intend to keep long after the program ends.

References

Crawford, L., Morris, P., Thomas, J., & Winter, M. (2006). Practitioner development: From trained technicians to reflective practitioners. International Journal of Project Management, 24(8), 722-733. https://doi.org/10.1016/j.ijproman.2006.09.010

Project Management Institute. (2021). A guide to the project management body of knowledge (PMBOK guide) (7th ed.). Project Management Institute.

Thomas, J., & Mengel, T. (2008). Preparing project managers to deal with complexity: Advanced project management education. International Journal of Project Management, 26(3), 304-315. https://doi.org/10.1016/j.ijproman.2008.01.001