Make your bed | lateralworks

Abstract

In May 2014, Admiral William H. McRaven told the University of Texas graduating class to start every day by making their bed. His point was not tidiness. It was agency: completing one small, controllable task creates momentum that carries through every task that follows. This paper draws a direct line from that lesson to the practice at the heart of every program lateralworks coaches — the weekly schedule refresh. Every complex development program operates inside a fog of uncontrollable variables: supplier delays, silicon errata, specification changes, resource constraints. Teams cannot control those events. They can control one thing absolutely — the cadence of their weekly schedule refresh. The refresh is a standing discipline, same day, same time, every week, in which every task owner reports an honest estimate against the schedule, the critical path is recalculated, and the core team decides on a specific pull-in action. The team walks out knowing exactly where the program stands. The paper makes three arguments. First, cadence matters more than content: the refresh derives its power from being non-negotiable, and the behavioral science behind small wins, peer accountability, and habit formation explains why. Second, the refresh only earns its cost when it is operationalized — lateralworks codifies a three-day rhythm that moves from honest task-owner updates, through critical-path analysis by the program manager and product delivery lead, to a forty-minute pull-in meeting and an AI-assisted status report. Third, consistent refresh execution builds compound returns in estimation accuracy, risk detection, and team confidence, visible week by week on the wigglechart. The argument rests on lateralworks’ experience coaching semiconductor and systems development programs since 1988 — including a three-year, multi-hundred-million-dollar joint development program that missed exactly one refresh in three years — cross-referenced throughout against published research on execution cadence, operating rhythm, and schedule management. An appendix reproduces a complete AI-generated weekly status report from a live program, end to end.

Foundation — The smallest task, the biggest signal

In May 2014, retired U.S. Navy Admiral William H. McRaven delivered a commencement address at the University of Texas at Austin that has since been viewed more than ten million times. His opening lesson was disarmingly simple: make your bed every morning. In SEAL training, instructors inspected every recruit’s bed before anything else. Corners squared, covers tight, pillow centered. A mundane act — and McRaven’s point was not about tidiness. It was about agency. Completing that first small, controllable task gave each trainee proof of accomplishment that carried through the rest of the day. It established a rhythm. It created evidence that discipline existed, and it gave people a reason to believe the next task was achievable. Accomplishing the first task, McRaven said, encouraged completing another, and then another.

The science under the anecdote McRaven’s lesson is a field observation, but the mechanism it describes is one of the most replicated findings in organizational psychology. Karl Weick argued in 1984 that people are paralyzed by problems framed at overwhelming scale, and that a strategy of “small wins” — concrete, complete outcomes of moderate importance — builds patterns that attract allies and lower the arousal that blocks clear thinking. A slipping two-year program is exactly such an overwhelming problem; a single week’s honest update is a small win. Teresa Amabile and Steven Kramer reached a parallel conclusion from nearly 12,000 daily diary entries by 238 professionals on creative teams: of everything that distinguishes people’s best working days, the single strongest factor is visible progress on meaningful work — even minor progress. Their “progress principle” is McRaven’s cascade, measured: small, regular evidence of forward motion compounds into engagement, and engagement compounds into performance. Charles Duhigg calls routines with this cascading property “keystone habits” — practices whose value lies less in their direct output than in the chain reactions they start. Bed-making is his canonical household example. And the habit-formation literature explains why the discipline must be consistent to stick: Phillippa Lally’s field study found that automaticity grows with repetition in a consistent context, reaching plateau after a median of 66 days — roughly the first quarter of running a new weekly discipline. This paper draws a direct line from that body of evidence to a lateralworks best practice that sits at the heart of every program we coach: the weekly schedule refresh. The refresh is the program’s keystone habit — the smallest task that carries the biggest signal.

The practice — Your project's made bed

Every complex development program — semiconductor, systems, or software — operates inside a fog of uncontrollable variables. Silicon may fail at characterization. A supplier may miss a delivery window. A specification may change under the team’s feet. Teams cannot control these events. But they can control one thing absolutely: the cadence of their weekly schedule refresh.

What the refresh is The refresh is a standing discipline, same day, same time, every week, in which every task owner on or near the critical path provides a realistic assessment of remaining duration, the schedule is updated, and the critical path is recalculated. The output is binary and public: the predicted end date has pulled in, held, or slipped — and the team sees which, every seven days. Five elements are mandatory, and section 06 codifies them: fixed cadence, live update, critical path review, end-date tracking on a wigglechart, and backup ownership so the cadence is never broken. Figure 1. The weekly refresh cycle. Five mandatory elements executed in sequence every week; backup ownership closes the loop so the cadence is never broken. What the refresh is not It is not a status call, and it is not a daily standup. A standup coordinates the work in flight today; a steering review allocates money and people quarter by quarter. The refresh does something neither of them does: it re-derives the program’s predicted end date from honest bottom-up estimates and forces a decision about how to move that date earlier. A meeting that ends with “we are three weeks behind” is a status meeting. A refresh ends with “here is the pull-in we chose on the critical path, here is the owner, here is the date”. The distinction matters because the failure mode of schedule governance is almost never the absence of meetings. Programs drown in meetings while the master schedule quietly fossilizes. A schedule that is not refreshed weekly becomes a historical document — it describes what was planned, not what is real. The refresh transforms it into a navigation instrument the team recalibrates every week, the way lateralworks’ long pole method treats the critical path as a target to attack rather than a report to file.

Why it works — Cadence beats content

McRaven’s bed-making ritual works because it is non-negotiable. It happens every morning regardless of what else is going on. The weekly refresh operates on the same principle, and its power comes from three properties: controllability, accountability, and biofeedback.

Figure 2. The three pillars of cadence. Controllability, accountability, and biofeedback compound over time into better estimates, earlier risk detection, and sustained program health. Controllability Every project has many uncontrollable factors. The team cannot prevent a supplier slip or a silicon bug. But running the refresh every week is entirely within the team’s control. It is the one scheduled event whose existence depends only on the team’s own discipline — which is precisely why it must never be canceled. When lateralworks coached a three-year, multi-hundred-million-dollar joint development program involving hundreds of people across multiple companies in the UK, the refresh was missed exactly once in three years: on Christmas Day. That record was not an act of heroism. It was a made bed, three years running. Accountability When people know they will report progress to their peers every week, behavior changes. FranklinCovey’s 4 Disciplines of Execution reaches the same conclusion from the same direction: its fourth discipline installs a short weekly session, separate from every other meeting, in which each team member answers for last week’s commitments and makes next week’s — because commitments made to teammates, rather than only to a manager, become personal. The refresh is that cadence of accountability applied to the master schedule. Each owner answers one question in public: did the work go as I said it would, and what is my honest date now? Biofeedback The refresh gives the team something most programs lack: a near-real-time signal of trajectory. After each update the critical path is recalculated and the predicted end date moves or holds. A team that watches its schedule pull in gains confidence and momentum — exactly the cascade McRaven described, and exactly

the progress principle in Amabile and Kramer’s data. A team that watches it slip gets an early warning measured in days rather than months. Early warning is the difference between a corrective action and a crisis. Why weekly — not daily, not monthly Cadence should match the tempo at which decisions must be made from new information. When General Stanley McChrystal’s Joint Special Operations Task Force fought a networked enemy, its operations and intelligence brief ran daily, ninety minutes, thousands of people across seventy locations — because combat intelligence decayed in hours. A development program’s schedule truth does not change hour to hour, but it changes far faster than a monthly review can catch: a month is long enough for a slipped task to compound through three dependent tasks and harden into the new critical path. A week is the interval at which schedule-grade information actually changes — long enough for real progress to measure, short enough that no slip is more than seven days old when the whole team sees it. Daily coordination belongs in the standup; weekly prediction belongs in the refresh; monthly and quarterly allocation belongs at the portfolio, where lateralworks runs the same refresh logic at lower frequency.

The lesson Start with the small task “If you want to change the world, start off by making your bed.” Admiral William H. McRaven University of Texas at Austin commencement, May 17, 2014

Mechanics — The three-day operating rhythm

A principle without mechanics is a poster. lateralworks operationalizes the weekly refresh as a three-day rhythm that fits inside a normal workweek and ends, every week, with a pull-in decision. Day 1 produces an update request. Day 2 turns task-owner responses into critical-path analysis and pull-in options. Day 3 runs a forty-minute core team meeting and issues the status report.

Figure 3. The three-day operating rhythm. The program manager’s outputs open and close the cycle; the pull-in meeting is where decisions are made and the schedule moves. Day 1 — post the update report The program manager (PM) generates and posts the update report to every task owner on the critical path and on any task scheduled to start, complete, or change state in the coming two weeks. Owners return their updates by close of business the same day. The report is intentionally short. For each task it asks three things: the current best-estimate finish date, the cause of any change from last week, and the top constraint blocking pull-in. It does not ask for percent-complete, because percent-complete invites negotiation. It asks for honest dates. The single-day window concentrates updates into one batch the PM can process on Day 2, instead of scattering them across chat threads and hallway conversations that never reach the master schedule. Day 2 — import updates and analyze the critical path The PM imports every returned update into the master schedule, then pairs with the product delivery lead (PDL) on critical-path analysis: which tasks now define the top three critical paths (CP1, CP2, CP3), what changed week over week, why, and where pull-in is possible on each path. The pairing is deliberate. The PM owns schedule mechanics and analytical discipline; the PDL owns engineering judgment — whether a pull-in option is actually feasible or a process step gates it. Neither role can prepare the pull-in meeting alone. Before the day ends, the PM sends the completed update report back to the task owners, so every owner sees their input reflected in the refreshed schedule. Visibility is what keeps the next round of updates honest. Day 3 — the pull-in meeting The full core team — the small, role-based team lateralworks puts at the center of every fast program — meets for forty minutes. The first twenty go to pull-in: the PM and PDL walk the team through CP1 through

CP3, the cause of each change, and the candidate pull-in options identified on Day 2. The core team decides. Actions get named owners and dates. The second twenty minutes go to technical issues, prioritized by critical-path impact; issues that do not touch the top three paths are deferred to a separate technical forum. Immediately after the meeting, the PM generates the weekly status report. Generation is AI-assisted: the inputs are the meeting transcript, the refreshed schedule, and the wigglechart trend visuals, and the structure is fixed — schedule status, trends, CP1–3, risks, actions. One document, five sections, the same shape every week. Appendix A reproduces one in full. Roles in the cadence Role Responsibility in the cadence Program manager (PM) Generates the update report (Day 1). Imports updates, analyzes the critical path, prepares pull-in options with the PDL, and closes the loop with task owners (Day 2). Runs the pull-in meeting and generates the AI-assisted status report (Day 3). Product delivery lead (PDL) Owns technical plausibility. Pairs with the PM on Day 2 to assess which pull-in options are engineering-viable. Leads the technical half of the pull-in meeting (Day 3). Task owners Return honest status updates by close of business on Day 1. Execute pull-in actions assigned on Day 3. See their updates reflected in the refreshed master schedule on Day 2. Core team Attends the forty-minute pull-in meeting. Makes pull-in decisions on CP1–3, resolves critical-path technical issues, and accepts the resulting actions and owners. Weekly inputs and outputs Day Inputs Outputs Day 1 Prior-week master schedule; list of tasks in scope for update. Update report published to task owners; owner responses returned by close of business. Day 2 Task-owner responses; wigglechart trend data; prior-week critical-path analysis. Refreshed master schedule; CP1–3 analysis with named causes; pull-in option slate; completed update report returned to task owners. Day 3 Refreshed schedule; CP analysis; pull-in options; meeting transcript. Pull-in decisions with owners and dates; updated risks and actions; AI-assisted status report distributed to stakeholders.

The instrument — The critical path, recalculated weekly

The refresh earns its forty minutes because of what it recalculates. The critical path method identifies the longest sequence of dependent activities from project start to finish — the one chain with no slack, the chain that sets the ship date. Whatever happens to that chain happens to the program. Everything else just watches.

The method is old enough to trust. Morgan Walker of DuPont and James Kelley of Remington Rand built critical-path scheduling between 1956 and 1959 to attack the cost of plant shutdowns, and DuPont cut shutdown costs by roughly a quarter with it. What has changed since 1959 is not the math but the cadence at which organizations bother to rerun it. The U.S. Government Accountability Office’s schedule assessment guide makes “updating the schedule using actual progress and logic” and “confirming that the critical path is valid” two of its ten best practices for a reliable schedule — a schedule that is not updated with actual progress at regular intervals cannot tell the truth about the program it claims to describe. The critical path is not static. It shifts as tasks complete faster or slower than planned, as scope changes, and as dependencies are re-sequenced. Near-critical paths — those within days of the critical chain — can silently become the new critical path if left unmonitored. lateralworks’ field data puts the danger zone at about ten days of float: paths that close sit one bad week from becoming the new long pole, which is why fast teams treat near-critical paths as critical and why the refresh reviews CP1 through CP3 every week, not CP1 alone. Weekly recalculation catches these shifts while corrective action is still cheap. The wigglechart: the trend is the instrument The projected end date is recorded at every refresh. Over time this produces the wigglechart — the weekly plot of predicted finish against target, and the single most information-dense artifact in the FTTM toolkit. The line wiggles; that is the name and the point. An honestly updated schedule moves every week. Each slip shows, gets attacked in the room, and recovers within weeks. A line that never moves is a schedule that has stopped speaking — a flat line is not stability, it is silence. Figure 4. Wigglechart: end-date trend over 26 weekly refreshes. The slate line converges as pull-ins land and banks the surplus by stepping the target down at week 17. The orange line diverges — and says so months before a quarterly review would. Read this way, the wigglechart is the early warning system every late project wishes it had bought in time. The comparison with a monthly reporting cycle is stark: a slip that lands on the wigglechart within seven days can hide inside a monthly cycle for four to eight weeks, filtered through status-slide optimism at every hop.

Figure 5. Feedback-loop compression. The same week-2 slip stays dark for weeks under a monthly review cycle; under a weekly refresh it is public within seven days, while corrective action is cheap.

Codification — Five elements, six design principles

Based on coaching more than two hundred development programs since 1988, lateralworks codifies the weekly refresh as five mandatory elements carried by six design principles. The elements are what a team does; the principles are why the mechanics hold up under pressure.

The five mandatory elements Fixed cadence. Same day, same time, every week. No exceptions. If the meeting owner is unavailable, a trained backup runs it. This is the make-your-bed discipline: the meeting happens regardless. Live schedule update. The schedule is updated during the cycle, not reconstructed after it. Each task owner provides a current honest assessment of remaining duration, and owners see the impact of their updates in the refreshed schedule the next day. Critical path review. After updates land, the team reviews the recalculated critical path. Has it changed? Are new tasks critical? Are near-critical paths closing in? The team agrees on pull-in actions where possible. End-date tracking. The projected end date is recorded at every refresh and plotted on the wigglechart. A converging trend signals a healthy program; a diverging or oscillating trend signals systemic issues that need intervention. Backup ownership. Every refresh facilitator has a designated, trained backup who runs the cycle without hesitation when the primary is sick or traveling. The cadence is never broken. The six design principles SME ownership of estimates is preserved. Task owners give honest best-estimate dates every week without being pushed to match a target. The gap between estimate and target stays visible in the schedule — knowing the gap is how you close it. The moment owners learn that estimates get negotiated to a target, the estimates stop being honest and the gap stops being visible. The critical path drives the agenda. Most schedule meetings allocate equal time to every task. This one does not. CP1 through CP3 get the airtime; everything else is deferred. That discipline is why forty minutes is enough. The core team’s attention is the scarcest resource in the program, and the cadence spends it only where it can change the outcome. Pull-in, not status. Status meetings end with “we are N weeks behind.” Pull-in meetings end with a chosen option, an owner, and a date. The cadence is named for what it produces: a week without a pull-in decision is a week the cadence did not run, even if the meeting took place on time. The same rule powers the long pole method’s refresh planning: attempt a pull-in every week, and bank the surplus so later slips land on the bank instead of the date. AI-assisted reporting keeps the load sustainable. The weekly status report is assembled from the meeting transcript, the refreshed schedule, and the trend charts, leaving the PM’s time for analysis rather than typing. Without that automation, a weekly cadence collapses under its own administrative weight within a month. With it, the marginal cost of the weekly report approaches zero while the format stays identical week over week — Appendix A shows the result. The loop closes on the task owners. Every owner sees their Day 1 update reflected in the Day 2 refreshed schedule. That is why the next Day 1 update is honest. Cadences that take inputs and never report back break the trust that keeps status honest, and the inputs degrade into what people think leadership wants to hear. Fixed day, fixed roles, fixed artifacts. The same day of the week, the same meeting length, the same report structure, the same distribution list. Variation costs attention; consistency buys it back. By Monday the core team should know exactly what the cadence will produce by Friday. This is the “consistent context” habit research identifies as the precondition for automaticity.

Normal organization vs. best organization Normal organization Best organization Schedule reviewed monthly or quarterly; slips surface on status slides weeks after they occur. Schedule refreshed weekly; every slip is public within seven days, raw, on the wigglechart. Meetings end with a status: “we are N weeks behind.” Meetings end with a decision: a pull-in option, an owner, and a date on CP1–3. Estimates negotiated toward the target; the gap disappears from view and reappears at the end. Honest bottom-up estimates; the gap stays visible and gets attacked weekly. Refresh canceled for holidays, travel, crunch weeks — cadence breaks under pressure. Trained backup runs the refresh; one miss in three years, on Christmas Day. Reporting consumes the PM; analysis happens if time remains. AI-assisted report generated from transcript, schedule, and trends; PM time goes to analysis.

Implementation — Standing up the cadence

The cadence assumes four things exist before week one: a core team that is formed, chartered, and meeting regularly; a master schedule in a tool that supports weekly updates and critical-path analysis; a wigglechart or equivalent trend visual that records milestone movement week over week; and a PM and a PDL — distinct individuals, each with time to do the Day 2 work well. If any one is missing, put it in place before starting. The cadence consumes standing artifacts; it does not recreate them.

Standing artifacts Four artifacts support the cadence from week one: the master schedule, the wigglechart, the risk register (feeding the risks section of the status report), and the action log (feeding the actions section). These are maintained continuously, not assembled weekly. The cadence updates them and consumes them. The first four weeks The first two weeks feel thin. Critical-path analysis is still calibrating, pull-in options are shallow, and task owners are learning what an honest update looks like. That is normal. By week three the updates stabilize. By week four the wigglechart begins to show the trend: either the gap is closing, or it is not. Either answer is valuable — if the cadence is surfacing that the team cannot close the gap, it is doing its job. It has turned an unnamed drift into a visible management problem. Figure 6. The calibration curve. Estimate quality and refresh maturity build asymptotically over the first month — the same shape habit research measures for automaticity under consistent repetition. Habit research offers one more encouragement and one warning. Lally’s participants who missed a single repetition did not reset the curve — one broken week does not destroy the discipline. But automaticity only built at all when the behavior repeated in a consistent context. Move the meeting around the calendar and the habit never forms. Fixed cadence is not a preference; it is the mechanism. Failure modes to watch The cadence fails in recognizable ways. Day 1 updates that trickle in after Day 2 mean the deadline is not being enforced. A pull-in meeting that spends its forty minutes on tasks outside CP1–3 means the PM–PDL preparation did not hold the agenda. A status report that never reaches the task owners is a broken output loop. And a core team that stops making pull-in decisions, week after week, points to a leadership problem the cadence cannot fix on its own — the instrument is telling the truth; someone has to act on it.

The test. Every week, one question answers whether the cadence is working: did the program make a specific pull-in decision on CP1, CP2, or CP3 this week? If yes, the cadence is doing its job. If the answer is no for several weeks running, the cadence is running without producing — and the root cause is upstream of the cadence.

Conclusion — From beds to programs

McRaven’s lesson resonates because it reframes discipline as a source of confidence rather than constraint. Making your bed does not change the world. But proving to yourself, every morning, that you can complete one task to standard — that you control at least one thing — creates the foundation for everything else.

The weekly refresh is your project’s made bed. It proves that the team can show up, report honestly, update the schedule, review the critical path, and walk away with a pull-in decision. Every week. Without exception. The discipline builds compound returns. Each week the team practices accountability, it gets better at estimating. Each week it reviews the critical path, it gets sharper at spotting risk. Each week it sees the trend line, it develops an intuitive sense of program health that no monthly steering committee can replicate. And the logic scales: the same refresh discipline that keeps one program honest runs at monthly cadence across the portfolio, where lateralworks applies it to project starts, rankings, and resource gates. Cadence is not one practice among the ten that fast teams share — it is the practice that keeps the other nine honest. Start small. Fix the day and the time. Post the first update report on a Day 1. Run the first forty-minute meeting on a Day 3, even if the analysis is thin. Then do it again next week, and the week after. The wigglechart will take care of the rest. Key principle. Never cancel the refresh. It is the one thing you can control. Make your bed.

A Appendix One week, one report: a worked example What follows is a complete, unedited weekly status report from a live semiconductor development program (identifying details generalized). It is the Day 3 output of the cadence described in section 04 — generated by AI skills within minutes of the pull-in meeting, from four inputs the cadence maintains anyway: the refreshed master schedule, the meeting transcript, the action log, and the risk register. Because the generation is skill-driven, the report has the same five sections in the same order every week: status summary, schedule and trends, this week’s tasks, actions, risks. Readers stop hunting and start comparing — week-over-week deltas jump out because the frame never moves. Note what the report contains that a hand-built status slide rarely does: named causes for every schedule change, the top three critical paths with float, a first material pull-in (23 days on the qualification milestone) traced to the specific replan that produced it, and seventeen open actions with owners and dates.

Appendix A, page 1 of 7. AI-generated weekly status report — example deliverable.

Appendix A, page 2 of 7. AI-generated weekly status report — example deliverable.

Appendix A, page 3 of 7. AI-generated weekly status report — example deliverable.

Appendix A, page 4 of 7. AI-generated weekly status report — example deliverable.

Appendix A, page 5 of 7. AI-generated weekly status report — example deliverable.

Appendix A, page 6 of 7. AI-generated weekly status report — example deliverable.

Appendix A, page 7 of 7. AI-generated weekly status report — example deliverable.

Sources

References

McRaven, W. H. Commencement address, University of Texas at Austin, May 17, 2014. Transcript at news.utexas.edu; video at https://www.youtube.com/watch?v=pxBQLFLei70
Weick, K. E. “Small Wins: Redefining the Scale of Social Problems.” American Psychologist, vol. 39, no. 1, 1984, pp. 40–49.
Amabile, T., and Kramer, S. The Progress Principle: Using Small Wins to Ignite Joy, Engagement, and Creativity at Work. Harvard Business Review Press, 2011.
McChesney, C., Covey, S., and Huling, J. The 4 Disciplines of Execution: Achieving Your Wildly Important Goals. Free Press, 2012. See Discipline 4: Create a Cadence of Accountability.
Lally, P., van Jaarsveld, C. H. M., Potts, H. W. W., and Wardle, J. “How Are Habits Formed: Modelling Habit Formation in the Real World.” European Journal of Social Psychology, vol. 40, no. 6, 2010, pp. 998–1009.
lateralworks. “Weekly schedule refresh cadence: a 3-day operating rhythm.” FTTM methodology brief, April 2026.
McChrystal, S., Collins, T., Silverman, D., and Fussell, C. Team of Teams: New Rules of Engagement for a Complex World. Portfolio/Penguin, 2015.
Kelley, J. E., and Walker, M. R. “Critical-Path Planning and Scheduling.” Proceedings of the Eastern Joint IRE-AIEE-ACM Computer Conference, December 1959, pp. 160–173.
U.S. Government Accountability Office. Schedule Assessment Guide: Best Practices for Project Schedules. GAO-16-89G, December 2015. https://www.gao.gov/products/gao-16-89g
McRaven, W. H. Make Your Bed: Little Things That Can Change Your Life… And Maybe the World. Grand Central Publishing, 2017.
Amabile, T., and Kramer, S. “The Power of Small Wins.” Harvard Business Review, May 2011. https://hbr.org/2011/05/the-power-of-small-wins
Duhigg, C. The Power of Habit: Why We Do What We Do in Life and Business. Random House, 2012.
lateralworks. “The long pole: find the path that sets the end date.” FTTM methodology white paper, July 2026. lateralworks.com/papers.
lateralworks. Internal assessment database. Engagement data across client programs, 1988–2026.
Fussell, C. One Mission: How Leaders Build a Team of Teams. Portfolio/Penguin, 2017.
lateralworks. “Starts control: balancing the portfolio for speed.” FTTM best practices white paper, July 2026. lateralworks.com/papers.
lateralworks. “The FTTM core team: roles, not functions.” Team series white paper, 2026. lateralworks.com/papers.
Project Management Institute. “Critical Path Method Calculations — Project Schedule Terminology.” PMI.org.
Mitchell, N. “The critical path you’re not watching.” lateralworks briefing paper, May 2026. lateralworks.com/papers/the-critical-path-youre-not-watching.pdf
lateralworks. “10 best practices of fast teams.” FTTM best practices series. lateralworks.com/papers/10-best-practices-of-fast-teams.pdf