Is there a methodology for axing methdologies? -


"itemprop =" text ">

How do you gather garbage or eliminate old and cumbersome ways that are more harmful than helpful to software development process? We do? How can you continuously streamline your process to get the programmer to actually get something instead of cleaning the way for the completion of closing a thousand barn doors of horses escaped because of last year?

Previous reviews to collect information about what works and what does not I will use You can use the past experiment at different points of your project cycle.

If you are using a repetition method, then you should have a retrospective at the end of each instance. . If you are using the waterfall, then you should do a retrospective (something called after it Morten) once the product has been released

During retrospective, you collectively respond to the following questions Needs:

  1. What worked well?
  2. What should we start?
  3. What should we stop doing?

After that, ask them what is important for them to prioritize to work with your team, that they are the one thing they want to change and start working on it We do.


Comments