As far as I can tell, _every_ software development process works if the people using it are well rested, knowledgeable, respect each other, agree on goals and methods, and have achievable deadlines. Just sayin'…
As far as I can tell, _every_ software development process works if the people using it are well rested, knowledgeable, respect each other, agree on goals and methods, and have achievable deadlines. Just sayin'… 8 comments
@gvwilson I agree. But I also think that the goal of a software development process is maximize those things, not consider them as inputs or complications to the process of shipping software. @gvwilson and they are paid startlingly well, the project interests them, is or isn’t a moral application of technology that inspires the crazy control need in each of them, includes the cool foods like hostess orange cupcakes, all kinds of toys, education payments and an excellent free medical and a startlingly g real bonus. |
@gvwilson these are definitely prerequisites, yes. I do think that an agile process, suited to the needs of the team and well-rounded through retrospectives that actually engender change, is a very valuable thing for keeping things cohesive.
That should be an outcome of the kind of system you are describing, but it helps to have leadership invested in continual improvement so that the "process" can be as optimal as possible.