Team Helios provides tips on effective development practices including design review tickets, focusing on quality over quantity, code reviews, unit testing, and managing builds in the staging environment. Design reviews should involve pair programming to catch edge cases and increase confidence. Quality is more important than completing tickets quickly, except for critical issues. Code reviews by at least one other person are important, and complex work should be reviewed by two people. Unit tests should be written before starting work and run locally to catch errors. No new tickets should be worked on after code freeze, and only the release manager should build in staging.

1. TIPS ON EFFECTIVE DEVELOPMENT
TEAM HELIOS
By Abhi Garg
Dun & Bradstreet Credibility Corp.
www.dandb.com

2. DESIGN REVIEW TICKETS
1. Before working on a ticket
2. While making adjustments to what was agreed upon
Advantages:
1. Edge cases are less likely to be overlooked
2. Pair programming is more efficient
3. Higher confidence level

3. QUANTITY VS QUALITY
1. Don’t rush into completing tickets
1. Quality trumps quantity*
*Conditions apply – i.e. critical issues that impact sales

4. CODE REVIEW AKA +1
1. This should not be overlooked
1. Small tickets can do with a single +1
1. Complex work (dev discretion) should have two +1s (use
story points as a guide)
1. Please avoid a verbal +1; important to leave a paper trail

5. UNIT TESTS
Highly recommend to write Unit Test before starting work on
a ticket
Very important to run unit tests locally before pull requesting

6. BUILDING IN STG
1. Let’s avoid new tickets after code freeze
1. Only RM (Release Manager) should build
in STG with Code Coverage person as a
backup