Being a happy developer

Introductory talk on Agile development and tips/tricks for daily developer happiness.

Transcript

1. Being a happy developer A field guide General Assembly - January 23rd, 2014
2. Topics Hello and some coordinates A small intro on agile methodology Weekly and daily work Tips to be a happy developer General Assembly - January 23rd, 2014
3. Hi! I’m Claudio And I work as a developer at New Bamboo General Assembly - January 23rd, 2014
4. What’s New Bamboo • Web agency • Mostly Ruby and Javascript • Strong developer culture Operations/MGM 5 Scrum Masters 3 Developers 15 General Assembly - January 23rd, 2014
5. What we do We build products WITH our clients We solve interesting problems (e.g. sentiment analysis, complex client side applications) We have fun doing it (most of the time) General Assembly - January 23rd, 2014
6. Agile terminology A fast primer General Assembly - January 23rd, 2014
7. Agile methodology A methodology to manage project with a focus on direct communication, working software, customer collaboration and quick response to change. General Assembly - January 23rd, 2014
8. Developers You guys! ! Decides the right way to build it. General Assembly - January 23rd, 2014
9. Product owner Owns the product vision. ! They decide the right thing to build. General Assembly - January 23rd, 2014
10. Scrum Master Available to help the team in any way the team needs. ! Removes obstacles from development, facilitates communication among the team and organises additional activities (retrospectives, backlog grooming, etc.) General Assembly - January 23rd, 2014
11. Backlog A collection of features that define the scope of the product. General Assembly - January 23rd, 2014
12. Story A way to express a feature from the point of view of the final user. ! So that I can have a career in software development As an aspiring developer I want to attend a General Assembly course. General Assembly - January 23rd, 2014
13. Sprint A short development iteration (1-2 weeks), in which the team commits to achieve a certain number of stories. ! Once started, a sprint should never be changed. General Assembly - January 23rd, 2014
14. Retrospective A specific moment at the end of a sprint where the team learns from what happened. General Assembly - January 23rd, 2014
15. How New Bamboo ship software Staging Production Development Done Done Done Current sprint Demo General Assembly - January 23rd, 2014
16. Working with your team Ideal for easier stories Requires code reviews Ideal for key stories Can skip review (not recommended) General Assembly - January 23rd, 2014
17. Velocity Measures team productivity Constant (constant growth) is better Often misused and abused General Assembly - January 23rd, 2014
18. Team rotation, scaling Rotations may decrease velocity (not always) Scaling up a team doesn’t necessarily improve velocity Plan rotations with momentum in mind Mentoring and training on live projects has an impact General Assembly - January 23rd, 2014
19. Now the big question How can I become a happy developer? General Assembly - January 23rd, 2014
20. My answer Be curious, ask questions Try to pair with experts Admit and learn from your mistakes Talk to people, especially clients Always think about the rest of the team Learn to embrace change Timebox everything General Assembly - January 23rd, 2014
21. –Kent Beck “Programming at its best is an act of empathy.” General Assembly - January 23rd, 2014
22. Good reads A. Hunt, D. Thomas - The Pragmatic Programmer - link ! On Agile: V. Subramanian, A. Hunt - Practices of an Agile Developer - link J. Shore, S.Warden - The Art of Agile Development - link M. Cohn - Agile Estimating and Planning - link H. Kniberg - Scrum and XP from the Trenches - link General Assembly - January 23rd, 2014
23. Contact me! @cloud8421 claudio@new-bamboo.co.uk General Assembly - January 23rd, 2014