After a plan is approved, execute all parts of the plan without stopping. Only stop for major problems, spending approval, or actions that cannot be undone.
By Pawan Nayar · from the LLOS AI Learning record
After a plan is approved, execute all parts of the plan without stopping.
Only stop for major problems, spending approval, or actions that cannot be undone.
A developer should run all parts of an approved plan one after another. Do not ask for approval between each small step. Only stop if a real problem blocks progress. Stop if a task needs more money. Stop if a task will change data permanently.
A developer has a plan to update a website. The plan has steps A, B, and C. The developer finishes step A. The developer does not ask, 'Ready for B?' The developer moves directly to step B. The developer only stops if a step needs a manager's approval for spending.
Resolved from this lesson's own record — real definitions, not invented for this page.
More from the same record, pulled by shared topic — not written new for this page.
A specification often tells a developer to copy an existing file. The developer should open that file first.
When a developer offers choices for a project, the developer must explain what each choice includes. This means describing what is new, what is reused, and what is uncertain.
A big content project takes many weeks. A developer should first test the new template.
A shareholder owns part of a company. A shareholder can vote on important company decisions.
After a plan is approved, execute all parts of the plan without stopping. Only stop for major problems, spending approval, or actions that cannot be undone.