| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Finally, you can manage your Google Docs, uploads, and email attachments (plus Dropbox and Slack files) in one convenient place. Claim a free account, and in less than 2 minutes, Dokkio (from the makers of PBworks) can automatically organize your content for you.

View
 

No Engineering Practices

Page history last edited by Luca Minudel 12 years, 1 month ago

 

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

Comments (0)

You don't have permission to comment on this page.