Going Agile: Brought to You by the Public Broadcasting System - Atlassian Summit 2010
•
2 likes•1,983 views
Going Agile: Brought to You by the Public Broadcasting System Tristan Mayshark, PBS Interactive
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (12)
Similar to Going Agile: Brought to You by the Public Broadcasting System - Atlassian Summit 2010
Similar to Going Agile: Brought to You by the Public Broadcasting System - Atlassian Summit 2010 (20)
More from Atlassian
More from Atlassian (20)
Recently uploaded
Recently uploaded (20)
Going Agile: Brought to You by the Public Broadcasting System - Atlassian Summit 2010
- 1. Going Agile with PBS
- 2. Public Broadcasting Service • 170+ member stations • 1500+ total websites PBS.Org / PBSKids.org (PBS Interactive) • national websites from Crystal City, VA • local server cluster in VA
- 3. Technologies • LAMP servers • Amazon Web Services / Rightscale • Redhat / CentOS
- 4. Tools • Komodo, Vim, Emacs • Atlassian Suite • Gliffy, Balsamiq, Theme Builder • SVN, Git, Gitorious • TestLink
- 5. About Me • Joined PBSi in 2008 • Tools management, infrastructure, QA • Comp Sci from SUNY Buffalo, 2005 • Background in IT / support, QA, coding / scripting
- 6. High Level Themes • Our dev process has gone agile recently • Atlassian tools used extensively • Process evolution has had clear benefits
- 7. Logins Per User, 9/08
- 8. Challenges in September 2008 • Jira was being used sporadically • No standard for QA process • difficult to have visibility • risk management = headaches • shifting priorities hard to track
- 9. PBS Video Player • Difficult vendor handoff and dev • Highlighted procedural problems
- 10. Needs as of Winter 2008 • insight into priorities • dynamic process that can adapt to unforeseen changes • infrastructure of software tools that facilitate collaboration • comprehensive solution for documentation
- 11. Evolution - Prioritization • weekly “greenlighting” • gives all parties visibility • Priorities xls in external SaaS repo
- 12. Evolution - Process • What is agile?
- 13. Agile - Definition • Empowering teams with the tools and communication to succeed • accepting that changing priorities are the norm • developing products in an incremental way • minimize time to market, maximize value per release
- 14. Agile Workflow - Envision • a several hour session where all project stakeholders identify the needs of end-users and suggest possible features • must-have, should-have or nice-to-have?
- 15. Envision
- 16. User Stories • Envision features become Jira stories • Assigned estimated point value (t-shirt size)
- 17. Iteration & Release Planning • Stories grouped into release • Releases broken into 2-week iterations
- 18. Stand-Up Meetings • Daily 15-30 minute meeting driven by GH task board
- 19. Bamboo • CI tool to automate builds, unit tests, UI tests
- 21. TestLink • Tracks execution of manual testing tasks • Ensures consistency of manual testing
- 23. Code Reviews • Fisheye/Crucible driven
- 24. Documentation Needs • Public data (announcements, available apps) • Externally relevant technical docs • Internally relevant product dev docs • Infrastructure / architecture docs
- 25. Enter Confluence • 4 basic spaces, plus team specific collab spaces
- 30. Tying it all Together
- 31. Access Control (Crowd) • Role driven (plus groups-by-role)
- 32. Overall gains • Visibility – internal and external • Transparency – better management of expectations • Efficiency – Improves as a direct result of above 2 points
- 33. Logins Per User, Revisited >>Past >>Present >>Future?
- 34. Evangelism (Utilization) • Jira, Confluence – dev, qa, product management, executive, infrastructure, external • Fisheye / Crucible – dev, qa • Bamboo – dev, qa • Crowd – Universal (invisible)
- 35. The Future • Jira API Work (Django based?) • Connecting Crowd to our own OID? • Further Standardization of processes?
- 36. The End! • Tristan Mayshark • PBS Interactive • http://www.pbs.org • ttdmayshark@pbs.org