Rich on Nostr: nprofile1q…targs [Edit] How to slow down software dev. - Ask for complete and clear ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqzdp33shl69xr0uq3x8n5gsjykq9upycwh6nqm02c3f6x0frrn0dqftargs (nprofile…args)
[Edit] How to slow down software dev.
- Ask for complete and clear requirements before you can do any work.
- Take the time to do exhaustive estimates of how long it will take.
- Come up with multiple different implementations.
- Ask the architecture team to review the implementations.
- Request input from the platform team.
- Make sure to get buy-in from all the stakeholders.
- Schedule meetings at inconvenient times, if the team is in multiple time zones make sure that someone will suffer.
- Schedule meeting times without checking calendars first forcing people to ask for (later) reschedules.
- Create a comprehensive QA plan with a full regression test-suite.
- Setup meetings with the UI team to define an API to use the new functionality.
- Use the full iterative UX design process, sketches with feedback, mockups with feedback, UX testing on prototypes.
- Do the first implementation based on incomplete or misunderstood requirements so that rework is required.
[Edit] How to slow down software dev.
- Ask for complete and clear requirements before you can do any work.
- Take the time to do exhaustive estimates of how long it will take.
- Come up with multiple different implementations.
- Ask the architecture team to review the implementations.
- Request input from the platform team.
- Make sure to get buy-in from all the stakeholders.
- Schedule meetings at inconvenient times, if the team is in multiple time zones make sure that someone will suffer.
- Schedule meeting times without checking calendars first forcing people to ask for (later) reschedules.
- Create a comprehensive QA plan with a full regression test-suite.
- Setup meetings with the UI team to define an API to use the new functionality.
- Use the full iterative UX design process, sketches with feedback, mockups with feedback, UX testing on prototypes.
- Do the first implementation based on incomplete or misunderstood requirements so that rework is required.