3 ms·
The problem is the future. Project Mgmt should at best be where are we now, and how did we get here. You can then use that to guesstimate how long the next st
by lifeisstillgood 5y ago
The problem is the future.
Project Mgmt should at best be where are we now, and how did we get here. You can then use that to guesstimate how long the next steps might take.
You can get all that out of your commit logs and tests.
Project Mgmt should not be about telling people what to do, but telling them they are doing the wrong thing.
- lifeisstillgood 5y agoA theory of Software Project Management: Working Features are all that matters. Working Features can be measured through automated tests. A Working Feature is complete if the set of tests that "verify" it are passing. The tests are tagged as verifying that feature, and likely include integration, performance and UI tests as well as unit. Honestly it does not matter if the tests are written before or after the code. (Its really hard to write tests for a UI element that does not exist yet.) How can I tell if people are working on the feature I want them to? You can read the code. But otherwise you cant.