Managing Software Development Projects with Jira.

Slides:



Advertisements
Similar presentations
> Sprint Planning Presentation API Release: Date: Presented by:
Advertisements

Connect Team Connect Team Outside Contrib Outside Contrib Unscheduled Backlog Bugs Feature Requests BA Review Requirement Docs Epic Large Tasks or Features.
JIRA Agile for Your Agile Implementation by Rajeswari Pandyram & Kevin Coughlan.
Agenda −Scrum with TFS 2010 using MSF for Agile 5.0 −Planning the Project −How do you plan the project? −Project planning in TFS 2010 −Planning a Sprint.
<<replace with Customer Logo>>
JIRA – An Introduction -Arpit Jindal
RTC Agile Planning Component
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
Project Management with TFS 1. What TFS offers for Project Management? Work Item tracking 2 Portfolio backlog Backlog Issue tracking Feature Product Backlog.
Visual Studio Online. What it Provides Visual Studio Online, based on the capabilities of Team Foundation Server with additional cloud services, is the.
1 The Database Application Development Process The Database Application Development Process.
Paul Coffey Employee Central Engineering Manager
Agile Survey GreenHopper 6 Demo Switch Q&A 3 June 2012 Agile Survey Scrum is still dominant > 50% 2 week sprints > 40% use story point estimates ~ 70%
Planning. SDLC Planning Analysis Design Implementation.
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
> Blueprint Kickoff >. Introductions Customer Vision & Success Criteria Apigee Accelerator Overview Blueprint Schedule Roles & Responsibilities Communications.
Case Study: Using JIRA & Greenhopper for Agile Development Jeff Leyser Atlassian Giancarlo Lionetti Atlassian Oren Teich Replicate Technologies Jean-Christophe.
JIRA Defect Tracking Tool Tool to Record, Track and Resolve Issues, Bugs, Defects, Improvements and New Feature Requests LIGO-G M.
CSCI ClearQuest 1 Rational ClearQuest Michel Izygon - Jim Helm.
TEAM FOUNDATION SERVER (TFS) By Sunny Niranjana Devi. M.
Sprint 114 Review / Sprint 115 Planning August 26th, 2013.
What is Scrum Process? Where is it used? How is it better?
DELIVERON CONSULTING SERVICES Getting Agile with Team Foundation Server 2010.
Planning and Tracking Projects with VSTS 2010 By Ahmed Nasr 1.
Sri Lanka Institute of Information Technology Software Engineering Project – I Clone of Rally GROUP NO : WD-SEP-002 | PROJECT NO :25 PROJECT : CLONE OF.
ZenTaoPMS(禅道) Introduction
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Software Project Management Team 04 – K15T2. Content Summarizing your view on “Software development process”. Answer 3 question: ◦ What is Software Development.
TFS 2010 What’s new and interesting. Key Items Agile Planning Tools – Slides #3-#6 Improved parallel development - Slides #7-#8 Continuous Integration.
JIRA usage in the DAQ An overview.
Sprint 108 Review / Sprint 109 Planning June 3 rd, 2013.
Managing Agile, Waterfall and Hybrid projects within the Portfolio
Theories of Agile, Fails of Security Daniel Liber CyberArk.
TFS 2015 – DAS Delivery model
WHEN TITLE IS NOT A QUESTION N O ‘WE CAN’ CA Agile Vision Product Manager Michael Lester.
Evan Leybourn STARTING WITH VSM & KANBAN A practical workshop on value stream mapping & WIP Starting with Value Stream Mapping and Kanban by Evan Leybourn.
AGILE - IMPLEMENTATION (C) CLARION TECHNOLOGIES. ability to move quickly and easily…. AGILE MEANING (LITERALLY)
1 Development with Agile methodology Scrum Lifecycle DEVELOPMENT PROCESS IN DROISYS INC.
1 Visual Studio Online for Cost Effective Code and Project Management Ravi Gudlavalleti.
#msdevcon Community Track IMPLEMENTATION OF SCRUM Bernardin Katić Insa Investment Software AG.
The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.
4/28/2017 JIRA Demonstration.
Scrum Process Proposal 1/16/09. User Stories Scrum Process Proposal.
Manage your projects efficiently and on a high level PROJECT MANAGEMENT SYSTEM Enovatio Projects Efficient project management Creating project plans Increasing.
PA Techcon: Project management
Ticketing essentials for Technicians at the University of Oregon
Agenda Learn about the new TJ Ministry Application & Registration System Mixture of PowerPoint Slides, Demo’s and Hands-on Goals: Learn Concepts Play.
Project Management with VSTS
Scrum and TargetProcess
Agile Scrum Management
PlaatScrum (Raspberry Pi scrum tool) Open Source Project
TFS Iteration Time Tracking and Reporting
Kanban Task Manager SharePoint Editions ‒ Introduction
Scaled Agile Requirements: What, When & How
So You Want to Be a Product Owner
Chapter 3: The Project Management Process Groups: A Case Study
Agile Planning and Work Management with VSTS
Inflectra User Summit San Francisco, CA Monday, April 16th, 2018
Summarizing Our Models to Date
WEBINAR: Integrating SpiraTest with JIRA
Simplified Development Toolkit
Quality Center (QC) 11 Training Global IT QA Testing Team 2013
Agile practices for documentation teams
Introduction to Agile Blue Ocean Workshops.
Microsoft Project Past, Present and Future
Requirement Management Automation with Atlassian Stack
SupportCenter Plus Product Overview.
CAD DESK PRIMAVERA PRESENTATION.
Scrum in Action.
Kanban Task Manager SharePoint Editions ‒ Introduction
Presentation transcript:

Managing Software Development Projects with Jira

2 Agenda Managing software development projects with Jira Types of projects Types of tickets Fields & Relationships SDLC: Kanban SDLC: Scrum Reporting Dashboards Add-ons

PROJECT TYPES

4 Ongoing support projects Projects with variable teams and release cycles When to use Project Types Kanban Benefits No waiting between tasks Less time shuffling resources Less time switching tasks

5 5 Active development projects with a consistent team and release schedule. When to use Project Types Scrum Benefits Iteration planning and monitoring Tracking sprint progress

TICKET TYPES

7 Ticket Types Epic When to use High-level organizational tool Measuring progress for a feature set Epic Story Sub-Task

8 Ticket Types Story When to use Define a single feature to be implemented in the system. When not to use Non-development activities Epic Story Sub-Task

9 Ticket Types Sub-Task When to use Breaking stories into smaller implementation tasks. When not to use On Simple/Short stories Tips Make titles of sub-tasks relate to the title of the parent story. Epic Story Sub-Task

10 Ticket Types Task/Technical Task When to use Non-development activities Spikes/Research activities When not to use On anything that will directly impact the system.

11 Ticket Types Improvement When to use Minor enhancements or adjustments to existing functionality. Small system tweaks of existing functionality. When not to use To add new functionality.

12 Ticket Types New Feature When to use Tracking requests for new features or functionality. When not to use To assign development work.

13 Ticket Types Bug When to use Tracking defects in the system. Includes both internal QA issues and end-user reported issues. When not to use For changes/enhancements to the system.

FIELDS & RELATIONSHIPS

15 Fields & Relationships Components When to use Relate tickets to various aspects of the system. Recommendations Per content type Per section/area of application Global elements (header/footer/Navigation) Per Role/Permission

16 Fields & Relationships Fix Version(s) Type 1 Type 3 When to use Tracking release(s) that the ticket was included in. Recommendations 1 release per sprint Use either semantic or date based versions. We use yyyymmdd.

17 Fields & Relationships Links & Relationships When to use Define relationships between 2 tickets. Provide links to documentation. Recommendations Define bug relationships. Provide links to docs/specs Define dependencies Point to similar tickets

KANBAN SDLC

19 Kanban SDLC Planning Board

20 Kanban SDLC Workflow

21 Kanban SDLC Reports & Monitoring

22 Kanban SDLC Reports & Monitoring: Issues Created Report

23 Kanban SDLC Reports & Monitoring: Resolution Time

24 Kanban SDLC Reports & Monitoring: Average Age

SCRUM SDLC

26 SCRUM SDLC Backlog View Tip: Name sprints as “Project Name Sprint 1”

27 SCRUM SDLC Active Sprint View

28 SCRUM SDLC Workflow

29 SCRUM SDLC Sprint Monitoring & Reporting

30 SCRUM SDLC Sprint Monitoring & Reporting: Burndown Chart

31 SCRUM SDLC Sprint Monitoring & Reporting: Epic Report

32 SCRUM SDLC Sprint Monitoring & Reporting: Velocity Chart

33 SCRUM SDLC Sprint Monitoring & Reporting: Created vs Resolved

REPORTING

35 Reporting Issues Worked On (EazyBI) Issues Worked On Hours Spent Per Issue

36 Reporting Budget Status (EazyBI) Kanban Style Scrum Style

37 Reporting Tempo Timesheets

38 Reporting Scrum Worklogs (Tempo: Excel Export)

Dashboards

40 Dashboards Developer Board

41 Dashboards Project Management Board

ADD-ONS

43 Add-Ons EazyBI Provides an extensive set of custom reporting options to Jira. Has an additional licensing fee. jira/cloud/overview

44 Add-Ons GitHub Usually built-in and already enabled, just needs to be configured. Displays branch, commit, and pull request info on your Jira tickets.

45 Add-Ons TrackDuck Allows client to report bugs directly from website. Captures user browser info and the page the issue was on. We’re looking for an alternative to TrackDuck though due to some platform stability issues and problems with the screenshot capture feature.

46 Questions

47 Thank You