Build.com Development Process

Transcript

1. Development@Build.com
2. Introduction
3. Who are we?
4. Smarter Home Improvement
5. Scott Senior Software Developer - Class of ‘04
6. Casey Lead Support Engineer - Class of ‘12
7. Brad Director of Software Development
8. Teams • Product Dev • Tools & Operations • Platform • International • QA • Support
9. Tools we use Aside from Sublime Text 2…
10. Atlassian’d
11. JIRA • Everything goes into JIRA • Nothing too small or too big • Time is estimated and tracked for all tasks • GreenHopper
12. Confluence • “Check the wiki…” • Braindump • Documentation • Planning
13. Bamboo • Can deploy individual branches from GitHub • Manage deployment across environments ◦ Sandbox ◦ Staging ◦ Production
15. Git & GitHub • Migrated from SVN in January • Git was a paradigm Shift • All commits have tracker IDs in the message
16. Dev Process
17. Methodology We have Agile / Scrum… sorta
18. Agile Use what makes sense for your org
19. Lifecycle of a Sprint Development Beta Release Week 2 Week 1 Week 3 Week 4 Planning
20. Sprint Planning • Meet at beginning of Sprint to plan • Break down tasks into small, manageable work • Estimate everything
21. Got everything? Okay, time to start working
23. “Tracker” Branches Dedicated branch for each JIRA issue
25. Start codin’
27. Spooning AKA Pair Programming
29. Coordinate with Clients • UX • Marketing • Sales • Operations • Brand Manager • Data
31. Standups • “What did you do yesterday?” • “What will you do today?” • “Is anything blocking you from completing your tasks?”
32. Finished codin’? Cool story, bro. Time for QA
34. Requesting QA • Must provide: ◦ Reference to Pull Request ◦ Relevant notes ◦ Requirements to test ◦ Steps to demonstrate that change is successful ◦ DO NOT ASSUME ANYTHING!
35. What does QA test? • Steps to reproduce error and ensure fix • Tests change across various browser • Tests deployment in Sandbox environment ◦ Depends on type of change ◦ Ensures no language version conflict CF8 vs CF10 • Coding Standards • Requirements/Process being followed
36. Code Review • Peer reviewed (team lead, etc.) • Ensures change follows coding standards • Completes the Pull Request merge
38. Sprint Ends …but things are just getting started…
39. Beta Testing • Internal • One Week • BETA is activated for a subset of internal users
40. Release Day • Pre-flight check to ensure any bugs from beta testing have been addressed • Red / Blue Strategy ◦ Easily rollback to previous deploy
42. Support Stuff • Direct contact for client's outside of SoDev • Bugs that made it into the wild, get reported to Support. • Support determines if the bug is data or code related, and fields the issue to correct department for resolution. • Creates replication steps and gathers any necessary info for the developer to do their job.
43. Questions? I am a Software Dev @ Build… AMA
44. Fin