Free Jira Scrum Kanban for Agile project to IT Professionals

• Attention - read course's description BEFORE taking it.

Info-statistics - present time, Jira software holds an estimated 85+% market share for the Agile projects, using Scrum and Kanban approach, Project Planning, Scrum Sprints, Test Planning,  Issue/Defect life-cycle and is used by around 90,000 companies worldwide.

This course is very pragmatic visual demo, designed as "hands-on" and "how-to" practically apply Jira for typical Agile project with Scrum Methodology needs, imitating hypothetical Insurance company Agile project activities.

During this course journey, I want students to acquire actual experience, how exactly, Agile project actors might utilize Jira, contributing to a project,  and how much time the full cycle might consume.

Note: 

• It is not necessary for you to repeat all of my Jira actor's actions.

• The objective is to familiarize you with possible Jira actual usage

• Jira is only a tool and the key to success is your personal knowledge of your organization's business

After brief Scrum Methodology fundamentals introduction or, if you already know, repetition, you will spend some time through visual journey, imitating Jira actions of the performing roles like: Product Owner, Scrum Team Developers, Scrum Master and potential Quality Assurance Analyst or Engineer.

Please note, that normally:

a. in the real large-scale companies productions environment, Jira will might be customized for the internal organization's needs by the specialists.

b. Medium-range companies, might use classical (course videos) unadopted version.

c. and small start-up companies, might utilize "off-shelf" Jira editions, procured from well-known Cloud Providers like Azure, AWS and GCP.

These visual demo journeys, relates directly to the following IT Industry employees:

• You are a Product Owner carrying the responsibility to contact customers directly and create Product Backlog, Epics and Business/User Stories for Agile project

• You are a Scrum Master, responsible for ensuring Scrum Methodology being implemented and followed during Agile project with mandatory Scrum training for  Team

• You are a Project Manager, who have been informed about Agile project incoming, which requires practical Atlassian Jira and Scrum process knowledge

• You are a Business Analyst, who is assigned to this Agile project, and is in need for fast-track practical Jira hand-on training

• You are a Scrum Team Developer with the responsibility to split User Stories from Product Backlog into Tasks, estimate, award story points, prioritize and assign to Sprint

• You are a QA Analyst, assigned to Team with responsibility to create Test Plan, Scenarios and Cases , execute such in Jira and report to the project management

• You are an IT Industry beginner, who needs to learn fast "how-to" Agile project, which requires practical Atlassian Jira and Scrum process knowledge skills

Remember: in real world, your actual Jira efforts outcome results, depend on personal knowledge of your organization's internal business.

Be aware:  in real world,  your Jira credentials will be auto-assigned by separate dedicated Administrator, and also such assignment will be released to the project group team members.

• Read-Only rights will be granted to project stakeholders

• Read-Write rights will be granted to project Product Owner, Business Analyst, Scrum Master, Team Developers, Quality Assurance Analysts, Acceptance Specialists and influential active participants.

Scrum Methodology related important notice:

• In Scrum, story points estimation, typically, follows a sequence using the Fibonacci sequence (0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89, 144, and go on..) to represent not time, but relative efforts, with each number representing a corresponding unit of complexity.

• Professional certified Scrum Masters are obligated to use above classical story points estimation technique.

• However, internally in your organization , you are free to equalize and assign story points to actual time estimated to be spent on a particular task, and thus, create, adopt and standardize your own story points sequence.

• After all, the Agile, means fast reaction with maximum flexibility, while Scum is an approach.