The W5HH Framework: Asking the Right Project Questions

UPI Study › Courses › Software Engineering › Free lessons › Lesson 13.6 Free with a free account

The W5HH Framework: Asking the Right Project Questions

Software Engineering · Chapter 13: Project Management, Planning, and Agile GovernanceSection 13.6 · lesson 85 of 1036 min · free with a free account

← Tackling Common Challenges in Software Project ManagementNext lesson: Estimating Timelines When Activity Durations Are Uncertain →

Earn 3 college credits for Software EngineeringRecommended for credit by NCCRS · Computer Science 301 · self-paced · one payment, lifetime access
Enroll in Software Engineering · $250 →Download the syllabus (PDF)

In this lesson

Not every planning tool is a chart - sometimes it's 7 questions.

  • Explain W5HH, and how it differs from a scheduling tool
  • Name the 7 W5HH questions, and what each surfaces
  • Apply the framework to a simple project
  • Explain why an unanswerable question is useful information

Transcript

Everything said in the video, section by section (764 words). Read along, or search it.

Project Management, Planning, and Agile Governance

The W5HH Framework: Asking the Right Project Questions

Not every planning tool is a chart. Sometimes the most useful thing a project can do, is simply make sure that seven basic questions all have real answers. This section covers the W five H H framework, and why its most valuable moment is when a question cannot be answered.

A Different Kind of Tool

Before Any Scheduling

A Gantt chart and a PERT chart both answer questions about timing and sequence. But they assume that scope and resources are already reasonably well understood. The W five H H framework, developed by software engineer Barry Boehm, addresses an earlier and more basic problem. It makes sure the project's fundamentals have actually been thought through, before scheduling any of it. The name comes from its seven questions. Five begin with W, and two begin with H. It is not a chart. It is simply a checklist.

Table 1

The 7 Questions

Here are the seven questions, and what each one is meant to surface. Why asks for the business reason the system is being built at all. What asks for the scope of what will actually be delivered. When asks for the schedule. Who asks who is accountable for each part of the work. Where asks where those responsible people sit, organizationally. How asks for the technical and managerial approach. And how much asks how much of each resource, like budget, effort, and time, the project needs.

Overlaps

Complements, Not Replacements

Two of these questions overlap with ground covered elsewhere. When corresponds to scheduling, covered through Gantt and PERT charts. And how much overlaps with estimating techniques. W five H H does not replace either of them. It simply insists that each question gets asked, as part of a complete picture, alongside the other five.

Table 2

Worked Example: A Feedback Portal

Suppose a company wants to build a customer feedback portal. Why? Complaints are scattered across email and phone calls, with no way to track them. What? A web portal where customers submit feedback, and support staff respond. When? A working version in ten weeks, ahead of the next launch. Who? One developer and one designer, reporting to the support team's manager. Where? Both sit within the support organization. How? Iteratively, with support staff reviewing a working version every two weeks. And how much? One developer, one designer, and a small budget for an email integration. Every answer is short and specific. W five H H is not asking for a lengthy plan, only for confirmation that someone can state each fundamental clearly.

Figure 2

When a Question Has No Answer

The real value of W five H H shows up, when a question does not have a ready answer. Ask each of the seven questions. If there is a clear, specific answer, that fundamental is confirmed. If there is not, that is not a failure of the framework. It is exactly the gap the framework exists to surface, early enough to do something about it. It shows where the project's real risk sits.

Not a 1-Time Checklist

Answers Go Stale

This is also why W five H H is not a one-time checklist, filled out at the start and set aside. Answers that were solid at the beginning can stop being true as work progresses. A who answer can go stale when a team member leaves. A why answer can shift when the business reason behind the project changes. Revisiting the seven questions periodically catches that drift, before it causes real damage.

Apply It

Nobody Can Answer Who

Let's apply that. For the feedback portal, the what and the why are both perfectly clear. But nobody can confidently say who is accountable for the portal's design. What does that suggest? It suggests real risk, regardless of how clear the other answers are. Without a specific person accountable, decisions can stall, or get made inconsistently. A clear scope and a clear business reason do nothing to prevent that on their own.

Key Terms

The Vocabulary of This Section

Let's lock in the key terms. The W five H H framework is a checklist of seven project questions, developed by Barry Boehm. Why, what, when, who, where, how, and how much. Project scoping is clarifying a project's fundamental reason, boundaries, and responsibilities, before detailed planning begins. And stakeholder accountability is clarity about which specific person is responsible for a given part of the project. That is the who question.

Key Takeaways

What to Carry Forward

To pull this together. The W five H H framework is a checklist of seven questions that confirm a project's fundamentals, before scheduling begins. It complements tools like Gantt charts, PERT charts, and estimating techniques. It does not replace them. Good answers are short and specific, not a lengthy plan. A question nobody can answer is valuable information, because it surfaces a real risk early. And the questions are worth revisiting, because answers drift as a project moves.

About Software Engineering at UPI Study

Software Engineering (Computer Science 301) is a self-paced online course of 103 video lessons in 15 chapters, from process models and agile to requirements, design, user interfaces, reliability, security and project management. It carries a NCCRS credit recommendation for 3 semester credits.

Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Enroll now → Course details Download the syllabus All Computer Science courses Every course with PRO →

Compare: Software Engineering vs Systems Analysis

Why take it here

Why students take Software Engineering with UPI Study

How professional software gets builtSoftware Engineering covers how teams turn requirements into working, maintainable software: process models, agile, requirements, design, testing, reliability and project management. It is a core course in computer science and software degrees.
Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.
Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.
Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.
Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.
130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Where the credit goes

Universities that work with NCCRS

Software Engineering carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Thomas Edison State UniversityThomas Edison State UniversitySigned partnerUniversity of the PeopleUniversity of the PeopleSigned partnerCharter Oak State CollegeCharter Oak State CollegeSigned partnerStrayer UniversityStrayer UniversitySigned partnerColumbia Southern UniversityColumbia Southern UniversitySigned partnerIndiana TechIndiana TechSigned partnerPenn StatePenn StateWorks with NCCRSSouthern New Hampshire UniversitySouthern New Hampshire UniversityWorks with NCCRSSUNYSUNYWorks with NCCRS +many more cooperating universitiesFind my college →

Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.

FAQ

Questions students ask us

About The W5HH Framework: Asking the Right Project Questions

What is the W5HH framework in project management?
The W5HH framework is a checklist of seven questions, developed by software engineer Barry Boehm, that confirms a project's fundamentals before scheduling begins. Its name comes from five questions starting with W (why, what, when, who, where) and two with H (how, how much). It is not a chart; it simply checks that each fundamental has a clear, specific answer.
What are the seven questions of W5HH?
The seven W5HH questions are why, what, when, who, where, how, and how much. Why asks for the business reason, what for the scope, and when for the schedule. Who asks who is accountable for each part, and where asks where those people sit organizationally. How asks for the technical and managerial approach, and how much asks for the budget, effort, and time required.
What does it mean when a W5HH question cannot be answered?
An unanswerable W5HH question signals real project risk, which is exactly what the framework exists to surface early. For example, if the why and what of a feedback portal are clear but nobody can say who is accountable for its design, decisions may stall or be made inconsistently. A clear scope does not fix a missing owner.
How does W5HH differ from Gantt and PERT charts?
W5HH confirms a project's fundamentals, while Gantt and PERT charts schedule work that is assumed to be already understood. Its when question overlaps with scheduling and its how much question with estimating, but it complements those tools rather than replacing them. It should also be revisited periodically, because answers such as who or why can go stale as a project moves.

About the Software Engineering course

How many college credits is Software Engineering?
Software Engineering (Computer Science 301) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
How much does Software Engineering cost and what is included?
$250, paid once, with lifetime access: all 103 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. Students who want several courses choose UPI Study PRO instead.
Which universities accept UPI Study credits?
UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.
How long does Software Engineering take?
It is self-paced with no deadlines. The 103 lessons total about 11 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.
How are the exams done?
Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.
How do my credits reach my college?
When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

Ready for the full course? Earn 3 credits in Software Engineering.

103 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.

Enroll in Software Engineering →Download the syllabusEvery course with PRO →
Software Engineering
3 credits · NCCRSEnroll →