Evolving Your Agile Process with Atlassian Tools - Atlassian Summit 2012
•Download as KEY, PDF•
0 likes•659 views
This document discusses going agile with Atlassian tools. It recommends keeping processes and workflows simple, with minimal issue types and workflow steps. It also stresses the importance of people over processes and automating tasks. The document cautions that Atlassian features are not always around the corner and not to depend on future capabilities. It provides advice on defining roles, processes, products and methodologies for agile teams using Atlassian tools.
Recommended
Recommended
More Related Content
What's hot
What's hot (18)
Viewers also liked
Viewers also liked (6)
Similar to Evolving Your Agile Process with Atlassian Tools - Atlassian Summit 2012
Similar to Evolving Your Agile Process with Atlassian Tools - Atlassian Summit 2012 (20)
More from Atlassian
More from Atlassian (20)
Recently uploaded
Recently uploaded (20)
Evolving Your Agile Process with Atlassian Tools - Atlassian Summit 2012
- 2. Going Agile with Atlassian …or, herding cats for fun and profit Jordan Dea-Mattson Director, Engineering Numenta, Inc.
- 5. It’s the People Stupid
- 7. It’s not about you!
- 9. If you want a job done right, automate it!
- 10. Why Atlassian?
- 11. “Atlassian has the worst possible tool suite, except for all the others… Winston Churchill Paraphrased and with apologies…
- 12. Atlassian is… • Adaptable • Open • Extensible • …but a a few words of caution
- 13. Trust, but verify… • Don’t depend on Atlassian futures • It is never, “Just around the corner…” • Don’t plan on it, until you have it in hand • It is never a… • Simple change • Enhancement • Addition
- 14. The Nitty Gritty
- 15. What kind of site? • Greenfield? • Urban infill?
- 16. What is your methodology?
- 17. What is your product?
- 18. Process Patterns • Abhor processes • Embrace patterns
- 19. A Process Pattern ! Keep it Simple! • Minimally viable process • Minimal Issues • Story, Bug, Technical Task • Minimal Workfow • Open, In Progress, Implemented, Tested, Deployed
- 20. Roles to Play
- 21. Visionary
- 22. Cat Herder
- 23. Score Keeper
- 24. Communicator
- 25. Closing Words
- 26. If it isn’t written down, it doesn’t happen
- 27. Your checklist! • Why do you want to do this? • Define a minimally viable process • What issue types do you absolutely need? • What are the minimal steps in your workflow? • What is the minimal information you must capture • Ruthlessly Pair Down
- 28. Questions?
- 29. Thank you!
Editor's Notes
- \n
- \n
- This slide can be used to break up the chapters of your talk - this would be the start to a new chapter\n- OR -\nThis could be used for making a single statement of a few words or a sentence.\n\nYou should choose one or the other, so that there’s a consistent system.\n
- \n
- At the heart of the Agile movement is a value on Individuals and interactions over processes and tools, as we design work to embrace Agile in our development practices, we have to keep this in mind. Scrum master certifications, JIRA workflows, and all of the rest have to be in support of the people.\n
- As noted in the Agile manifesto, “Simplicity--the art of maximizing the amount of work not done--is essential.” If we want to get folks to embrace changes in process and working style, it has to be simple and easy to do so…\n
- Why are you doing this? What does this gain for the team? How does this make the team more productive and efficient? \nWhatever you do can’t be exclusively about your needs and desires as a project manager or manager. It has to be aligned with the team’s needs.\n
- How is what you are asking the team to do aligned with their interests? \nThe path of least resistance is to make sure that interests are aligned.\n
- The only way to get repeatable results in any system is to automate it.\nThe only way to get people to do something consistently is to automate it.\nA half day of automation work will save you days of aggravation and pain down the road. \nIf you don’t have the skills to automate things, start gaining them now.\n
- \n
- \n
- Everyone has their reasons, here are some of mine.\n
- \n
- \n
- \n
- \n
- \n
- \n
- Stealing from lean processes, let’s look to having a minimally viable process. \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- fin\n