Stitcher for Podcasts

Get the App Open App
Bummer! You're not a
Stitcher Premium subscriber yet.
Learn More
Start Free Trial
$4.99/Month after free trial

Show Info

Episode Info

Episode Info: Done can mean a lot of different things, depending on who you ask or when you ask them. If you ask a programmer if they are done with a feature they may say ‘yes’ because they are done coding it or ‘no’ because it has yet to be tested and they know there will be adjustments needed after or during testing. According to the Agile Alliance the definition of done is something which the team agrees upon, such as a list of criteria, which must be met before a task or story is considered “done”. Defining done helps a team to understand where they are in the process of development. This helps to eliminate going back into a codebase because it doesn’t meet expectations. However, overly obsessing over a list of items can be counter-productive. It needs to define the minimal criteria to meet the expectations of the business or customer. Also, each story or feature may have it’s own specific criteria of what it needs in order to be done. On the other hand, if the general definition is too loose then it will not be an effective measure. These are a fun, light hearted, way of thinking about the serious topic of when to stop working on something. It can be hard to stop when you know there is more that can be done. On the other hand sometimes you are just done with a task or have too much on your plate to give it the attention that it needs. Figure out where your coding practices fall and make an effort to improve them. Episode Breakdown Well, It’s Just an Idea This is your starting place for building or working on something. It’s more than a dream but not quite a reality. You’ve written it down, even mapped out what you are going to build. You have a blue print of what you want to build. There are likely several diagrams and documents. This is the point that the SCRUM stories of Kanban cards get created. It’s very rare that you would stop here. You might stop if after writing it down you realize that the tools or technology you need to build it does not exist or is not possible. In other cases you may be given incomplete information. This could be from poor or missing acceptance criteria. Lack of steps to reproduce a bug. Whatever the case, if you don’t have all the information needed then you are done before you really get started. You may perceive a need, write it out, then when taking it to the business find out they don’t need it or have other processes in place and don’t need it. A lot of times stopping here usually means that you are putting it to the side for now. This is a starting place for your project, story, or task. You will most likely keep going from here. This is the planning phase. If you aren’t planning out your stories and tasks you need to start. It will help you know where to go and get to done quicker. Worthy of Momma’s Fridge “You’re proud of it, your momma’s proud of it, but that’s about it.” You threw something together, maybe your very first attempt at a new technology or at coding a ...
Read more »

Discover more stories like this.

Like Stitcher On Facebook


Episode Options

Listen Whenever

Similar Episodes

Related Episodes