How not to write the definition of done:
* The new functionality is implemented.
* Producer & Leader have reviewed it.
This says nothing useful, and is generic enough to apply to every story.
"When it works and is reviewed, it is done"
Life of a Noob Dev Op, as I learn to code and work on getting a job in a new industry
How not to write the definition of done:
* The new functionality is implemented.
* Producer & Leader have reviewed it.
This says nothing useful, and is generic enough to apply to every story.
"When it works and is reviewed, it is done"
Work is them asking for a program to do a thing.
It starts off bare bones, and gets more and more complex and complete each day.
And then one day it is done, and you turn it over to be run by an automated system, or other people.
Later, they ask you to make some changes, so you open up the files and try to understand why you wrote that, and this does what?
Eventually you make the changes, and hand it off again, not to think of it till they want more changes.
Me: I know how to do this. I have done it multiple times over the last couple of years.
Me 20 minutes later: OK, I think I missed a step... or 10. OK, off to read my notes... or should I just google it?
Me 30 minutes later reading "Hello World" at one of my favorite websites: http://127.0.0.1:5000/
And now, because I have been thinking about Flask, I have Flash (Gordon) by Queen playing in my head.
How not to write the definition of done: * The new functionality is implemented. * Producer & Leader have reviewed it. This says noth...