PrOpER [coach]

posted in: coaching | 0

Problem: Pick a problem to work on. Watch how the team works. What needs to be improved? Options: Consider your options. What could you try that might influence the situation for the better? List at least three options. Experiment: Pick … Continued

Code Style [coach]

posted in: coaching | 0

Collective code ownership is easier when the team follows a consistent approach to design and coding style. We’re not saying that they need to create a formal coding standards document. They simply need to establish a “house style” that everyone … Continued

Explain refactoring [coach]

posted in: coaching | 0

Refactoring is the activity of improving software design without changing its behaviour.   A team may never need to explain what refactoring is to their customer, if they manage to keep applying small refactorings as part of each story. However, … Continued

Making time for design [coach]

posted in: coaching | 0

Far more often than analysis paralysis, we find teams suffer from the opposite problem: not spending enough time on design. Developers can be tempted to skimp on design because software design is invisible from the outside, so the customer can’t … Continued

1 2 3