Jira Agile Project Management for Beginners-+ Confluence

gile methodology is designed to solve several problems in software development, including:

1. Lack of customer involvement: Agile methodology emphasizes regular customer collaboration, which helps to ensure that the software being developed meets the needs of the customer and is aligned with their business objectives.

2. Late discovery of defects: Agile methodology emphasizes iterative development and testing, which allows defects to be discovered and addressed early in the development process, rather than waiting until the end of the project.

3. Inflexibility: Traditional software development methodologies are often inflexible, making it difficult to respond to changing requirements or market conditions. Agile methodology is designed to be adaptable and flexible, enabling teams to respond quickly to changing circumstances.

4. Lengthy development cycles: Agile methodology emphasizes incremental development and delivery, which allows software to be delivered to the customer in smaller increments, reducing development time and enabling early value delivery.

5. Poor communication: Agile methodology emphasizes communication and collaboration among team members, which helps to ensure that everyone is on the same page and working towards a common goal.

Overall, Agile methodology is designed to help software development teams deliver high-quality software that meets customer needs, while also improving development speed, flexibility, and communication.

In this section we will be focusing on the problems that Jira solves.  In the past project would run for years and when they were done it was not what the customer wanted.  Agile changes that.

The Agile Manifesto is a set of guiding values and principles for Agile software development that emphasizes iterative and incremental development, customer collaboration, and the ability to respond quickly to change. It was created in 2001 by a group of software developers who sought to improve upon traditional project management methodologies, which they saw as slow, inflexible, and lacking in customer focus.

The four values of the Agile Manifesto are:

1. Individuals and interactions over processes and tools

2. Working software over comprehensive documentation

3. Customer collaboration over contract negotiation

4. Responding to change over following a plan

These values are supported by twelve principles, which emphasize the importance of delivering working software frequently, embracing change, empowering self-organizing teams, and maintaining a focus on customer needs. The Agile Manifesto has become a widely recognized framework for software development, with many organizations adopting Agile methodologies to improve the efficiency, quality, and customer satisfaction of their software development processes.

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

Agile is used in software development for several reasons, including:

1. Faster time-to-market: Agile methodology emphasizes iterative development and continuous delivery of working software, which can significantly reduce time-to-market for new products or features.

2. Increased customer satisfaction: Agile methodology emphasizes regular customer collaboration, which helps to ensure that the software being developed meets the needs of the customer and is aligned with their business objectives.

3. Improved quality: Agile methodology emphasizes continuous testing and integration, which helps to identify defects early in the development process, leading to higher quality software.

4. Increased flexibility: Agile methodology is designed to be adaptable and flexible, enabling teams to respond quickly to changing requirements or market conditions.

5. Improved team collaboration: Agile methodology emphasizes communication and collaboration among team members, which can improve team morale and productivity.

6. Reduced development costs: Agile methodology emphasizes incremental development and delivery, which reduces the risk of costly project failures and enables teams to deliver value early in the development process.

Overall, Agile methodology is used in software development because it provides a flexible, iterative approach to development that emphasizes customer collaboration, continuous delivery, and quality. This approach can help development teams to deliver high-quality software that meets customer needs, while also improving development speed, flexibility, and communication.

Jira is a popular project management tool used by many software development teams. Here are some of the key Jira terminology:

1. Issue: In Jira, an issue is a unit of work that needs to be completed, such as a bug, task, or feature request.

2. Project: A project is a collection of issues in Jira. Projects can be used to organize work by team, product, or department.

3. Workflow: A workflow is a series of steps that an issue goes through in Jira, from creation to completion.

4. Epic: An epic is a large body of work that can be broken down into smaller tasks or issues.

5. Sprint: A sprint is a fixed period of time during which a team works on a set of issues or tasks.

6. Backlog: A backlog is a list of issues that need to be completed, but have not yet been scheduled for a sprint.

7. Board: A board is a view of the issues in a project, typically used to track progress and prioritize work.

8. Dashboard: A dashboard is a customizable view of project metrics and progress, typically used to provide an overview of project status.

9. User story: A user story is a short, simple description of a feature or functionality from the perspective of the end user.

10. Assignee: An assignee is the person who is responsible for working on a particular issue or task in Jira.

In this section we will be focusing on estimating a project in Jira.   This is how you estimate how long a user story will take.

Scrum is a framework for Agile software development that emphasizes teamwork, collaboration, and iterative development. Here are some of the key Scrum roles and team norms:

Scrum Roles:

1. Product Owner: The Product Owner is responsible for defining the product vision, prioritizing the product backlog, and ensuring that the team is delivering value to the customer.

2. Scrum Master: The Scrum Master is responsible for facilitating the Scrum process, removing impediments, and helping the team to work effectively together.

3. Development Team: The Development Team is responsible for building the product, working collaboratively to complete items from the product backlog in each sprint.

Team Norms:

1. Daily Scrum: The Daily Scrum is a short daily meeting where team members provide status updates, identify any impediments, and plan their work for the day.

2. Sprint Planning: Sprint Planning is a collaborative meeting where the team selects items from the product backlog to work on in the upcoming sprint.

3. Sprint Review: Sprint Review is a meeting where the team presents the work completed during the sprint and gathers feedback from stakeholders.

4. Sprint Retrospective: Sprint Retrospective is a meeting where the team reflects on the previous sprint and identifies areas for improvement in their processes and collaboration.

5. Timeboxing: Timeboxing is a technique used in Scrum to set fixed time periods for meetings and activities, helping to ensure that the team stays focused and productive.

6. Collaboration: Collaboration is a key component of Scrum, with team members working together to complete tasks and overcome challenges.

Overall, Scrum roles and team norms are designed to promote collaboration, accountability, and continuous improvement, helping teams to deliver high-quality software that meets customer needs in a timely and efficient manner.

Sprint Planning is a key activity in Agile software development, particularly in the Scrum framework. Here's an overview of Sprint Planning and its key components:

What is Sprint Planning? Sprint Planning is a collaborative meeting where the Scrum team works together to define the work that will be completed during the upcoming sprint. The goal is to select a set of product backlog items that the team can realistically complete within the sprint, based on their capacity and the priority of the work.

What are the key components of Sprint Planning?

1. Sprint Goal: The Sprint Goal is a brief statement that describes the objective of the sprint, and provides guidance for the team to focus on what needs to be achieved during the sprint.

2. Product Backlog Review: The team reviews the product backlog, which is a prioritized list of user stories, bugs, and other work items that need to be completed. The team and the Product Owner work together to ensure that the highest priority items are at the top of the backlog.

3. Capacity Planning: The team estimates their capacity for the upcoming sprint, based on their availability and any other commitments they may have. This helps the team to determine how much work they can realistically take on during the sprint.

4. Sprint Backlog: Based on the Sprint Goal and the team's capacity, the team selects a set of items from the product backlog that they will commit to completing during the sprint. These items are then moved into the sprint backlog.

5. Sprint Plan: The team creates a plan for how they will complete the selected items during the sprint. This plan may include breaking down user stories into smaller tasks, identifying dependencies, and estimating the effort required to complete each item.

Overall, Sprint Planning is a collaborative process that helps the Scrum team to focus on the highest priority work, establish a shared understanding of the sprint goal, and create a plan for how to complete the work during the sprint.

In Jira, user stories are a key component of Agile software development, and are used to define the features and functionality that will be delivered in the product. Here's an overview of user stories in Jira:

What are user stories? User stories are short, simple descriptions of a feature or functionality from the perspective of the end user. They are typically written in a format that describes the user, the action they want to take, and the benefit they will receive.

For example, a user story might be: "As a customer, I want to be able to view my order history so that I can track my purchases."

How are user stories used in Jira? In Jira, user stories are typically added to the product backlog, which is a prioritized list of work items that need to be completed. The Product Owner is responsible for defining and prioritizing the user stories, based on customer needs and business goals.

During Sprint Planning, the team reviews the product backlog and selects a set of user stories that they will commit to completing during the sprint. The team then breaks down the user stories into smaller tasks, estimates the effort required to complete each task, and creates a plan for how to complete the work during the sprint.

As the team works on the user stories, they update the status of each story in Jira, so that the Product Owner and other stakeholders can track progress and ensure that the team is delivering value to the customer.

Overall, user stories are a key component of Agile software development in Jira, and help to ensure that the team is focused on delivering features and functionality that meet the needs of the customer.

Agile defines success in terms of delivering value to the customer in a timely and efficient manner. Here are some key components of success in Agile:

1. Customer satisfaction: Success in Agile is measured by the degree to which the customer is satisfied with the product or service that is delivered. The goal is to continuously deliver value to the customer, and to respond quickly to their changing needs and requirements.

2. Business value: Success in Agile is also measured by the degree to which the product or service delivers business value. This might include increased revenue, improved efficiency, or reduced costs.

3. Iterative delivery: Success in Agile is achieved through iterative delivery of working software or product increments. This allows the team to get feedback from the customer early and often, and to make changes as needed to ensure that the product meets their needs.

4. Collaboration: Success in Agile is also measured by the degree to which the team is able to collaborate effectively to deliver the product. This might include regular communication, shared ownership of the product, and a willingness to adapt to changing circumstances.

5. Continuous improvement: Success in Agile is not a one-time event, but a continuous process of improvement. The team should be constantly seeking feedback, learning from their experiences, and making changes as needed to improve their processes and deliver better products to the customer.

Overall, success in Agile is measured by the degree to which the team is able to deliver value to the customer, collaborate effectively, and continuously improve their processes and products.

Learn more about scrum.   Download the scum guide.

We will go over the difference between a company and team project

Describes how to sign into JIra Software and look at clasic and new Get Views

Rove AI Jira new

How Jira Rovo AI works

1. Refreshed Design & Brand Updates

   • Atlassian has rolled out a refreshed design system: updated typography, more readable fonts, and clearer heading levels. Atlassian Design System+2Atlassian Documentation+2

   • Icons are more streamlined, shapes and sizes more consistent with the new design style. Atlassian Design System

   • Colour palettes and component styles are being tweaked to align with the new Atlassian brand identity. Some of this is still being previewed/testing. Atlassian Design System

2. Navigation & Layout Changes

   • The sidebar is becoming more prominent and consistent across views (home, project, issue). It’s expandable/collapsible, user-customizable. University IT+2Atlassian Documentation+2

   • Project view moving from left-side menu into top level in some layouts. Also, hovering behaviour changed (e.g. star/unstar projects on hover) rather than buried in menus. University IT

   • “Home”, “Projects”, “Issues” etc. pages are being updated to have more consistent look & feel, with improved UX (less clutter, clearer navigation). Atlassian Community+2Atlassian Documentation+2

3. Terminology Changes & Language

   • Atlassian is reducing use of the word “issue” in many contexts, in favor of more universally understood language like “work”. Atlassian Documentation

   • The “Parent Link” and “Epic Link” fields are being replaced / unified into a single “Parent” field in many views and exports. Atlassian Documentation

4. Functional UX Improvements

   • Smart Links are now available in more fields (URL / short text fields) and in more views (list, board, backlog) so linking is more versatile. Atlassian Documentation

   • New toolbar for bulk actions in the issue navigator: select multiple issues and perform Edit / Change status directly from toolbar. Atlassian Documentation

   • Collapsible sections on issue (work item) pages to reduce scrolling and allow users to focus on essential content. Atlassian Documentation

   • Better in-product help: search terms are highlighted in help results so users can more quickly see relevant information. Atlassian Documentation

5. Project / Form & Template Customization

   • Admins in team-managed projects can now create custom fields while building forms, without needing to go into separate project settings. Atlassian Documentation

   • More form fields, options for making fields optional or required, and more guidance for form users. Atlassian Documentation

   • Project templates are being simplified and made more flexible (bundles, better previews) so creating new projects is faster with less manual setup.

We describe how to use a Jira Scrum Board and a Jira Kanban board.

Jira Project Managent, Jira Software, Agile Scrum.

Jira Software and Project Management

In this section we will be focusing on what velocity is and what the reports look like. 

In this section we will be focusing on projects and how to use them.  

In this section we will be focusing on lira and kanban.  In the rest of the course you will learn Jira, Agile, Scrum, Agile Project Management, Kanban, Bug Tracking, Agility and Project Tracking.  What is Jira and how to use it, what is Agile Project Management, overview of Agile Definitions, what is difference between Scrum and Kanban, how to create tasks, how to create epics, how to create Sub-Tasks, howto create sprints, and explain what a velocity chart is.

In this section we will be focusing on process control and how use it.   

In this section we will be focusing on bug tracking.   I

Learn how to use the Your Work Section, Filters and Dashboards