Main Menu
- Introduction
- 1. Introduction
- Overview, Definitions and Terminology
- 2. The first step in the DevIps methodology
- 3. Brief history of the traditional SDLC
- 4. Problems solved using DevOps
- 5. Rethinking the SDLC with DevOps
- 6. Factors driving DevOps acceptance
- 7. New challenges of the DevOps methodology
- Comparison to traditional SysAdmin roles
- 8. Hardware provisioning
- 9. Configuration management
- 10. Creating storage and databases
- 11. Providing security
- 12. Virtualization
- 13. Operations
- DevOps Processes
- 14. Introduction to the DevOps workflow
- 15. Requirement gathering with DevOps
- 16. The DevOps development cycle
- 17. QA and user acceptance testing
- 18. Application deployment using DevOps
- 19. Using DevOps for maintenance and release scheduling
- DevOps functions and groupings
- 20. Using HipChat for distributed team management
- 21. Using GitHub for collaboration
- 22. Sharing software issues with JIRA
- 23. Aligning teams using confluence
- 24. Sharing code with Bitbucket
- 25. Managing cross-platform development with DevOps
- 26. Practice: Setting up a DevOps Environment
- Creating and running an Agile project in JIRA
- Section 1
- 27. Projects keep your work organized
- 28. Creating an account with Atlassian
- 29. Project creating and management
- 30. Schemes, screens, workflows and permissions
- Section 2: Managing all those work items
- 31. Epics, stories, bugs and tasks
- 32. Issue type attributes, adding and removing them
- 33. Managing your backlog
- 34. Creating and configuring your board
- 35. Creating and starting a sprint
- 36. The daily scrum
- 37. Smaller stories or tasks
- 38. Closing the sprint – the sprint report
- 39. Burndown report
- 40. Sprint report
- 41. Velocity chart
- 42. Release and epic burndown
- 43. Version and epic reports
- 44. Issue searching using JQL
- 45. Saving and managing filters
- 46. Executing bulk changes
- 47. Creating new boards from saved filters
- 48. Creating and managing dashboards
- 49. Adding gadgets to your dashboard
- 50. Sharing your dashboard
- Section 1
Terms and Definitions
Burndown: How many story points are completed over a period of time.
CISO: Chief Information Security Officer
DevOps: The union of Development, Operations along with R&D and Security with the purpose of building collaboration between teams to reach a common goal
DVCS: Distributed Version Control System
Epic: A large Story that likely spans multiple Sprints
JQL: JIRA Query Language, similar to SQL
Operations: Team responsible for provisioning hardware, networking, OS and Patching
PaaS: Platform as a Service
RAD: Rapid Application Development
Ready: Optional organizational Sprint named ‘Ready’ that contains the collection of fully Refined issues that have acceptance criteria in them. These can then be moved from the “Ready” sprint to a fully defined Sprint.
Refined: All issue questions have been answered and everything that describes what this thing is have been defined.
Release: A Version that has been deployed. Releases may contain multiple Epics.
Scrum:
SDLC: Software Developement Life Cycle
Sprint: Collection of issues that are Ready
Story Points: Refer to the Doubt, effort and complexity contained within a item. Higher values = more difficult, more time consuming, etc.
UAT: User Acceptance Testing
Vagrant: Virtualization automation deployment tool. Works with most hypervisors such as VMware
Velocity: Number of story points your team can complete in a Sprint
- This value should be modified as the project progresses.
- If you cannot complete the required number of story points in a sprint, you should lower your velocity.
- Conversely, if you can do more, increase your velocity.
Version:
Work Item: (JIRA) Stories, bugs and tasks
Yesterday’s Weather
- The average of the velocities of the previous 3 Sprints to “forcast” the maximum velocity of the next Sprint.