Join Robert Anthony for an in-depth discussion in this video What you should know before watching this course, part of Planning and Releasing Software with JIRA.
- [Instructor] Let's go over what you should know before starting this course. You should already have a firm understanding of how Jira works. This means you have used Jira extensively in the past to create issues, search for data, and generate reporting via dashboards and standard scrum and kanban boards. This will help you keep up with the navigation between different sections of the software. You should understand basic Jira administration concepts like issue type configuration, workflows, and project administration. This will help you as we go through the different project configuration elements of our instance.
You should also understand advanced Jira administration concepts like advanced workflow design, reporting, and screen configuration. You should also understand how to install other pieces of software in your Jira instance. This will help you jump in when we start configuring our demo instance and installing add-ons. It would also be helpful if you understand the basics of scrum and agile development to better understand some of the terms we will be going over, but it isn't a must. We aren't focusing on the actual development work in this video, but rather how an experienced Jira administrator manages this cycle within the software itself.
We will do this by looking at three different areas. The core boards functionality allows for versioning and creating releases for specific projects, while also allowing for time measurement. The popular add-on Portfolio, allows for board-type management of projects on a larger scale, providing a 5,000-foot view of multiple projects within an instance. The repository connected software, Bitbucket, allows for automated pushing and pulling from development environments initiated by custom workflow triggers and post functions. Let's have a quick overview of some of the software development terms we'll be touching on.
Agile development is a type of project management, usually used in software development, it divides larger tasks into smaller pieces of manageable work for the purposes of tracking and efficiency. It's widely recognized as a highly collaborative method of releasing a product, while maintaining an updated schedule or estimation. Continuous integration, or CI, is the process in which each developer's work is developed in parallel. It's done in independent branches that are then combined into a main development branch at the end of a pre-determined period. Continuous delivery, or CD, adds on to the CI process.
Taking it a step further and allowing for developer's work to be released in a pre-determined time period. This release to a live product is performed after either an automated or manual QA testing cycle. Continuous deployment, also known as CD, is the next logical step of these processes, allowing for an automatic push of each developer's work after an automated testing cycle. This determines the work is ready for release, having no failures reported for automated testing. Now we won't be going over in any great detail what I've just covered.
Rather the assumption will be, you already know how these pieces work, as we cover how to build off of that knowledge to extend your configuration options using Jira.
- Creating new Jira boards
- Creating cross-project release plans in Portfolio
- Managing Portfolio dependencies
- Configuring Bitbucket for code management and version control