Why your developers are slow
jeremyphelps.com
jeremyphelps.com
If a developer becomes suddenly unproductive burnout is often the culprit.
Also, in my experience another culprit is: your developers are slow because you aren't willing to pay them market rates or show them respect so even though their conscious mind wants to work their butt off for you, they just can't do it because moral is so low.
My target audience is founders of very early-stage startups, so I cut the section under the assumption that they probably won't have much technical debt yet.
Early-stage startups tend to have rampant technical debt for two reasons:
1) They need to get a product to market immediately and they need to iterate on it rapidly—so using technical debt as a tool to achieve short-term goals quickly is actually awesome.
2) Startups tend to pivot. Making fundamental domain changes to a product quickly tends to give you very weird systems, often with large unused portions.
Please don't unless you can make sure it won't make your devs miss lunch or leave late because it got extended.
I'd prefer to just schedule meetings ahead as a suggestion.
Managers don't get that you waste time if you put a sewer canal in the street, close the street and pave it, then break it up again to put cables in.
Can anyone point me to a succinct resource for non-developers on writing product requirements?
Yes, please don't !