Timeline for Task estimation for PMs who are not developers
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 8, 2019 at 16:57 | comment | added | user85627 | The prototyping stage is really for exploring high risk features. Features that are low risk will be similar to things done before so no need to prototype. The goal of the prototype stage is not to fully produce the feature, but to attempt it. Attempting to build a feature and discovering that it's much harder than first thought is an OK outcome at this stage. As per agile, each feature attempt is time boxed. Start with high risk/high priority and move to high risk/lower priority within a sprint. At sprint boundaries consider alternatives where a feature could not be built in time. | |
| Feb 8, 2019 at 14:21 | comment | added | Sarov | What do you do when you have low-risk, high-priority features and high-risk, low-priority features? How do you reconcile? | |
| Feb 8, 2019 at 11:35 | review | First posts | |||
| Feb 8, 2019 at 14:21 | |||||
| Feb 8, 2019 at 11:31 | history | answered | user85627 | CC BY-SA 4.0 |