No Engineering Practices

 

1. Smells

• Technical Debt is accumulating
• Dis-agreements break out over formatting etc.
• Code is never reviewed.
• No one knows if the build is currently working.

 

2. Discussion

 

The team is in the dark about the state of their code.

 

3. Causes

• Adoption of Scrum without a team member experienced in agile practices and without guidance from an experienced instructor
• ...

   

4. Consequences

 

5. Prevention

 

6. Example Remedies

• Agree on team standards for code formatting, variable naming etc.
• Do pair programming
• Do code reviews for code not written in pairs
• Start doing Test Driven Development
• Set up a Continous Integration machine

 

7. Case Studies

 

Credit: this is based on material from the personal experience of Mark Levison