23. Why?
• Collaborate - everyone works at the same
time
• Distributed - everyone has a copy
• Versioning - your embarrassing moments
are kept forever
• Github - SAAS / Cloud
High Cost \n- Initial Design\n- Iterating \n\nBrings focus away to small details\n- color, logo, etc \n
- quick to build and change\n- lots of templates of common \n- low amt of details focuses on UI / UX\n- less is really more\n
\n
\n
\n
\n
\n
\n
\n
\n
Involve the customers & developers\nBreak app down into small ticketsAssign high priority tickets to current sprint\nEvery release should be USABLE\nLet the client play with it & report bugs\n\n
\n
\n
\n
\n
\n
Why ?\n- so your colleagues wont accidentally break your code\n- good documentation on how your creation works\n\n
Why ?\n- so your colleagues wont accidentally break your code\n- good documentation on how your creation works\n\n
Why ?\n- so your colleagues wont accidentally break your code\n- good documentation on how your creation works\n\n
Why ?\n- so your colleagues wont accidentally break your code\n- good documentation on how your creation works\n\n
Why ?\n- so your colleagues wont accidentally break your code\n- good documentation on how your creation works\n\n
- Continuous Integration\n-- Runs Related Test whenever the codebase changes\n
\n
\n
\n
\n
- weed out problems that could take production down\n- test features in the right environment... Development doesnt help\n