When a feature is approved, a developer must build and deliver the complete feature quickly. A developer must not ask for approval at each small step. A working, even if imperfect, feature is more useful than a perfect feature delivered late.
By Pawan Nayar · from the LLOS AI Learning record
When a feature is approved, a developer must build and deliver the complete feature quickly.
A developer must not ask for approval at each small step. A working, even if imperfect, feature is more useful than a perfect feature delivered late.
Once a feature is approved and a budget is set, a developer should build and ship the entire feature. Do not stop to ask for permission at every small step. The user wants to see the full working feature. The user will give feedback on the complete feature. This feedback helps improve the feature.
A manager asks a developer to build a new 'Quote' tab. The manager approves the idea and budget. The developer should build the entire tab, from pasting text to showing voiced outcomes. The developer should not ask for approval after building only the paste function. The manager wants to test the full tab, even if it has small issues.
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 developer should release new features quickly. This allows a manager to give feedback right away.
A complete design specification provides all necessary details. It lists changes to the user interface.
A design specification gives clear instructions. It describes how the product should look and work.
The AI model records feedback when a user types '#Log This'. The AI model writes 1-3 notes about that moment.
When a feature is approved, a developer must build and deliver the complete feature quickly. A developer must not ask for approval at each small step. A working, even if imperfect, feature is more useful than a perfect feature delivered late.