Page: 'Alderwood Relaunch — Task Board'\n\nIn Progress:\n- Homepage copy (Tom) — updated 1 day ago, in final review.\n- Case study template (Fieldstone/Jess) — updated 1 day ago, finally moved after chase-up email, first draft shared.\n- Pricing page dev build (Marcus) — updated today, all 3 components done, in QA.\n- Dev environment setup (Marcus) — updated 2 days ago, finally completed.\n- Blog redesign scope (unassigned) — still no owner, no updates in 12 days.\n- ROI calculator widget (Marcus) — new card, added this week, status 'not started', no owner confirmed yet.\n\nDone:\n- Homepage wireframes (Fieldstone)\n- Kickoff call notes (Priya)\n- Sales pricing alignment doc (Priya + Sales team)\n- Stock photography selection (Priya)\n\nBlocked (explicitly marked):\n- Case study interviews with 2 customers — one customer responded, interview scheduled for tomorrow. Other customer still hasn't replied, 9 days now.\n\nAuto-detected: Most items moved in the last 2 days following the vendor chase-up. Blog redesign remains untouched at 12 days with no owner. The new ROI calculator card has no owner and no timeline yet, added but not yet planned.

Summary  
This chapter teaches how to parse a collection of records, compute derived properties such as elapsed days since the last update, and generate a flagged tabular report highlighting stale or unassigned items.

General domain of usage  
Project management and progress tracking

Still Priya on the Alderwood relaunch. Earlier in the course you dug into the task board to find the one thing that was quietly stuck. This is about seeing everything at once — so next time something stalls, you notice in a day, not eight. You'll turn the raw board into a clean tracker with owners, status, and how long each item has sat untouched.

The task board is connected as a tool for this chapter. It's the same shared board from earlier in the course, now a bit further along. Here's the current state, so you can see what Claude is turning into a tracker:

Note

1 day ago — moved after the chase-up, first draft shared

One scheduled; one customer silent 9 days

>### Task
> 
> Ask Claude to read the task board and build a tracker with task, owner, status, and days since last update — flagging anything stale or ownerless.
 >
>**Prompts to Try**
 >
>><b>Read the Alderwood relaunch task board and build a tracker with task, owner, status, and days since last update. Flag anything over 5 days or with no owner.
 >
> Tracking your own project instead? Describe your board, then ask:
>
>><b>Build a tracker with task, owner, status, and days since last update, and flag anything stale.
>
>**What you're aiming for:** a clean table — task, owner, status, days since last update — that flags the stale items (blog redesign untouched for 12 days) and the ones with no owner (blog redesign, and the newly added ROI calculator). It should end by naming the one thing to check again tomorrow. When you have a tracker that surfaces problems at a glance, you're done.

Discover how to keep a real project from falling apart: turn a messy brief into an actual plan, catch budget and schedule problems before they bite, push back on scope creep, and keep your team coordinated under a hard deadline. You'll practice it all through a live website relaunch, with Claude helping you plan, defend, and coordinate the work end to end.

Get hands-on experience turning a scattered project brief into a task list, then checking that plan against a real calendar and a real budget before you commit to a deadline.
 

Discover how to defend a deadline against scope creep, find the task that's quietly stuck, and chase down a vendor who's gone quiet — before any of it becomes a crisis.

Master the skills needed to research the competitive landscape, update stakeholders clearly, track the whole team's progress in one place, and coordinate a final sprint under pressure.