3 ms·
I appreciate there must be some environments where what is required is well understood and relatively stable. Actually there isn't. Every project, no matter ho
by onion2k 10y ago
I appreciate there must be some environments where what is required is well understood and relatively stable.
Actually there isn't. Every project, no matter how it's managed, changes as it goes on. It has to because you learn and discover things along the way. That's why maintaining and understanding project requirements and how they've changed is incredibly important. If you don't keep on top of them then you end up with a project that wanders all over the place and never finishes. Or you build something that misses out important features. Or the project costs far too much. Requirements are not tasks, or epics, or things you're working right not. They're the goals that the tasks and epics work towards.
(My first startup was a requirements management app.)
- webmaven 10y ago> (My first startup was a requirements management app.) How did that work out? In the 90's it seemed every industry was switching to Documentum for that sort of thing.