2 ms·
Excellent overview. (But just an overview, there's a lot more meat on these bones.) These are the things that go without saying, but no one talks about becaus
by edw519 18y ago
Excellent overview. (But just an overview, there's a lot more meat on these bones.) These are the things that go without saying, but no one talks about because they aren't cool.
A spec is well written when QA can figure out how to test a feature based on the spec.
A great test of your specs. Building test plans and development should be able to proceed simultaneously and separately.
On gathering data, go out and talk to people getting more data points about the problem you are solving until you start hearing the same things and can’t learn more from talking. Then go work on it, knowing all this data.
Don't forget to talk to them in groups. Their disagreements (and there will be disagreements) will provide some of your best data points.
Niel doesn’t recommend a developer also taking on the role of PM, as there needs to be a tension between who represents the user and who implements the product.
What he calls tension, I call checks and balances. We hackers are all too familiar what could happen when you develop in a vacuum.
The PM should be the most empowered employee in your company… Yes, even more than the CEO
This cannot be lip service. The first time the CEO overrules the PM, your "project management" will lose all credibility and be worthless.
- wastedbrains 18y agoYeah, I don't follow everything he outlined. I think being able to do testing with out a formal spec is good. Especially when talking about unit level testing. Once you are talking about functional testing it is better to have an outline of what exceptions and expectations should exist in the system. Good point about talking in groups, letting potential clients argue over a feature and resolve what they both think is best can be gold. It is a great way to force people into some potentially different ideas.
- edw519 18y agoIt is a great way to force people... It's also a great way to find out what's already going on. How could you be expected to extract data points before they even agree with each other?
- wastedbrains 18y agoIn the end I don't expect them all to agree... but yeah finding out what they are already feeling and agreeing about is important. It is also really good to see what they completely disagree about.
- iron_ball 18y agoIronic as hell. As the programmer, I'm also generally the only person looking out for the user. Our project managers only care about hitting every bullet point on the invoice and coming in on budget.