Your SlideShare is downloading. ×
GreenHopper for DevOps
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

GreenHopper for DevOps

4,857

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
4,857
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
25
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • First off, who has had difficulty delivering a new software release sometime during the past three months?\n\nOkay... if you want to deliver value fast you need DevOps. DevOps is a hallmark of a high performing team. When Devs and Ops are always fighting, everybody looses.\n\nOver the next 10 minutes we will take a look at four things:\n- the DevOps movement\n- a successful Atlassian case study\n- how GreenHopper and kanban can support a DevOps team\n- and steps to kickstart a DevOps culture in your organisation\n
  • DevOps movement started around two years ago to overcome an “Us VS Them” mentality\n- there was an approach where Developers would ‘throw stuff over the wall’\n - for instance, you may have heard things like ‘well it works on my machine’\n- Ultimately, this behaviour is a result of the structure of the organisation.\n - Developers report to a VP of Engineering, Operations reporting to a VP of Operations. Surprise surprise.\n\nFurther, the goals and incentives for Developers and Operations folks differ.\n- Developers want change, progress and new features. Whereas, \n- Operations wants stability, uptime and security.\n\nA recent study on DevOps cites a number of key reasons people are joining the movement:\n- Lowering the mean-time-to-resolution for defects\n- Improve team communication\n- More frequent and smoother software upgrades\n- Matching Agile development with Agile delivery\n\nHappy medium between the cornerstone of DevOps and is necessary to deliver value fast.\n
  • JIRA Bugfix\n- Shared definition of done with build engineers (our Operations folks)\n - we added “Awaiting Deployment” queue to show value being built up and not delivered to customers\n - 10 days from when all of the bugs have been fixed, value is ready, and when it is released for customers\n- Extended CI to include Continuous Deployment\n - automation of deployment steps speeds delivery and minimises errors\n - one click, rather than three days of pain\n - we are getting better all the time\n\nKanban as a methodology\n- Lots of DevOps teams use Kanban\n - visualise the workflow\n - limit WIP\n - continuous improvement\n- These steps work for scrum teams as well\n\nHere is how I use GreenHopper...\n
  • Redefine Definition of Done to include delivery of value to customers\n- It is now a shared Definition of Done\n- Relies upon Devs and Ops to get to Done\n\nAs an aside, this is the new Rapid Board, note:\n- The busted WIP limit\n - There is too much work in progress and the WIP limit for In Review is at capacity\n- The “Expedite” swimlane\n - One issue is a Blocker\n - Configurable based on JQL\n\nIncidentally, we hope the Rapid Board will be our answer to support for multiple JIRA projects.\n- Based upon JQL query\n- It is in testing in Labs today and we are seeking feedback from kanban teams first and foremost. \n\n \n
  • Another step is visualising work queues and build up\n- We don’t want lots of issues in To Deploy, or In Review for that matter\n- At a glance you can see the number of issues in each column on a given day\n\nEnsure a smooth flow of issues across the board\n- using column constraints\n- speed work across the board using an expedite, or similar, swimlane\n\n
  • Consistency and predictability of delivery.\n\nMeasure how long an issue is In Progress for using the Cycle Time chart\n- are we getting better or worse at delivering?\n- are our stories smaller or larger?\n\nUse cycle time to get a handle on delivery of value. Keep pushing for speed.\n\nOptimise the whole system, not just a portion of the system.\n\nHere are three things that we learned from our journey that I want to share with you, to help you with your DevOps movement...\n
  • Steps that you can take:\n\nIt’s a human problem, it is all about trust. Get out of your seat and use your two feet.\n\nGet over our differences and work together on delivering value to customers.\n\nCollaboration with people you trust\n- shared definition of done\n- allow Ops to write code (Collective code ownership)\n- show Devs how the software is deployed - no more ‘well it works on my machine’, give Devs the tools to deploy like production\n\nDevelopers - know what is happening in production - Google Analytics, NewRelic, Splunk\nOperations - know what is on the horizon - attend a sprint or release planning session\n
  • DevOps - developers and operations working in harmony, working to deliver value to the customer.\n\nWe are still learning. We are still adapting.\n\nDon’t ever think you are done, this is a continual process. Start by taking the first step.\n\nThank you.\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Transcript

    • 1. GreenHopper for DevOpsLean + Agile + Automation = DevOpsNicholas Muldoon (@nickmuldoon)Product Manager, Atlassian 2
    • 2. “...organisations which design systems ... areconstrained to produce designs which are copies of thecommunication structures of these organisations ” Conwayʼs Law, Melvin Conway 3
    • 3. Case Study - JIRA Bugfix• Redefine Done• Visualise Flow• Measure Delivery 4
    • 4. Redefine Done SCREENSHOT OF A 7 COLUMN RAPID BOARD 5
    • 5. Visualise the Flow 6
    • 6. Measure Cycle Time SCREENSHOT OF A 7 COLUMN RAPID BOARD 7
    • 7. Working Together• Restore trust• Share the source• Clear visibility 8
    • 8. “ devops is continuous learning from others continuous improvement of oneself continuous deployment to production ” #summit11 9
    • 9. 10
    • 10. Questions? 10

    ×