JIRA 5.x, first steps
|
|
- Bennett Butler
- 6 years ago
- Views:
Transcription
1 JIRA 5.x, first steps Table of Contents: 1.) Change History: ) URL: ) Login: ) Setting user profile: ) Using filters:... 4 a) Changing existing filters ) Configuring your dashboard:... 5 a) Choose another already existing dashboard... 5 b) Create / change your own dashboard ) Creating a JIRA entry... 6 a) Projects... 7 b) Issue types... 7 c) Issue fields Summary Story Points Priority Due Date Desired Delivery Date Description Components Assignee Config Inquiry by Affects Version/s To be informed after creation To be informed later / To be informed later Build No Fix Version/s Steps to reproduce Epic / Theme Flagged Attachment Publication Range tallard JIRA first steps (2).docx 1/20
2 d) Notification ) Versioning (for developers only) a) Version number b) Build number ) Agile Workflow (for developers only) a) Agile boards Product Backlog / Priority of work (Scrum view): Work view (without swimlanes): Work view (with swimlanes): b) Workflow structure Scrum workflow c) Workflow actions Description of classic view: Transitions and Actions (classic view): Priority of work (classic view): Priority of work (agile boards): Transitions and Actions (agile board): Creation of own agile boards: ) Change History: o Version 2.5; May 08, Changes: o o o o o Paragraph 2.) URL: Change the URL address Paragraph 4.) Setting user profile: Minor rework on how to change your profile in the beginning Paragraph 7.) b)setting user profile: Issue types: Minor rework on Issue types. Added Story and Epic to the description. Paragraph 7.) c) Issue fields: Minor rework on fields Flagged, Assignee and Inquiry by. Added field Story Points. Renewed pictures for field Epic / Theme. Paragraph 7.) 7.d) Notification: Moved from 9.) c) Workflow actions a) Paragraph 9.) a) Agile boards - Product Backlog / Priority of work (Scrum view): The priority of work is described by the positioning in the actual Scrum board. After an issue is moved from Backlog to an actual Sprint the product owner prioritizes the issues. The issue at top has the highest priority. tallard JIRA first steps (2).docx 2/20
3 In the Scrum Plan board you change the priority of an issue by click-and-hold the item with the mouse and move them to a higher position. In the Scrum workflow a developer always chooses the highest positioned issue and works on it. - Work view (without swimlanes): The image above displays a possible view of the Scrum board in Work mode (without so called swimlanes ). This view offers a maximum of overview. - Work view (with swimlanes): tallard JIRA first steps (2).docx 3/20
4 In another possible view (see picture above) swimlanes are activated. You see all issues in order of their priority and existing sub-tasks strictly assigned to the main issue. With this visualization all developers see which issue has the highest priority (that is not always clear in the view without swimlanes!) and which sub-tasks of a story belong to one issue. o o Workflow structure: Major rework on Workflow structure. Changed the structure from the classic workflows to Scrum workflow. New description and new picture added for Scrum workflow. Paragraph 9.) d) Workflow actions: Major rework on Workflow actions. Added description of classic view, priority of work and transitions & actions for classic and Scrum view. 2.) URL: - JIRA: - Official JIRA manual: - Official Greenhopper manual (agile development plugin for JIRA): 3.) Login: Use Windows Login data for login. Please contact AO Technics in case you still encounter problems. 4.) Setting user profile: Go to your login name displayed on the above right corner, click on the sign to the right of it and then on Profile : There you may want to change your preferences (like language change) by clicking on the Edit pencil: tallard JIRA first steps (2).docx 4/20
5 Please change your Avatar with a fitting profile picture (this is important especially for developers). Optionally also change language. It is strongly adviced to change preferences as displayed below (unless you want to receive plenty of s): 5.) Using filters: You probably don t want to use only the see all issues filter which is active at start. tallard JIRA first steps (2).docx 5/20
6 It s highly recommended to create and save your own individual filters and you can even share them. At first, click on the issues (German: Vorgänge ) field (not the sign beside it): Your left frame should look like the picture above. If not, just click on the New Tab below and then, if the frame still doesn t look like above, click on Switch to simple search. Now you can select all those fields you want to filter for and click on Search button. If you like that filter, you should save it by clicking on Save. a) Changing existing filters Unfortunately, Filter handling in JIRA is not very user-friendly. You can do it as followed: o click on the issues field (not on ) o click on Edit tab above o change your filter as desired o Click on button Search o Click on Summary tab o Click on Save as or Save tallard JIRA first steps (2).docx 6/20
7 6.) Configuring your dashboard: There are two ways to set up your dashboard: Choose and load an already existing dashboard (which is strongly recommended for foreign users) or create your own one. a) Choose another already existing dashboard o Just click above left on the sign beside of Dashboards and then on Manage Dashboards. o Click on the left on Search o For foreign users: Type in your country name (e.g. Spain ) o Select your dashboard. b) Create / change your own dashboard Your dashboard is your JIRA start screen and you are invited to reconfigure it as your wishes. Just click above left on Dashboards (not the sign beside it), then to the right on Tools and finally on Create Dashboard : Enter a name for your dashboard and click on Add. Afterwards click above right on Add Gadget : There are plenty of (more or less) useful gadgets here. But one of them is highly recommended to install: the gadget Column order. Choose it and click on Add it now. If you have finished all your gadgets click above right on Finished. You now need to configure your Filter results gadget. Select under Saved Filter one of those filters you have saved before (see point 5.) and click finally on Save. Your gadget could look similar to the image below. If you want to edit your gadget again, you need to click on the gadget s above right corner on the sign and then on Edit : tallard JIRA first steps (2).docx 7/20
8 7.) Creating a JIRA entry A JIRA entry is called issue (German: Vorgang ). Just click on the above right corner to create one: a) Projects If you don t know which project is relevant, just choose project AO_Inbox. Issue will then be assigned to the relevant project later on. b) Issue types Some remarks regarding issue types (in case of doubts use Task (No QA! ): - Issue type Task (No QA!) is only for issues that don t require any programming (related to the project). Caution: Task (No QA!) issues will never be tested by QA! Choose another issue type if QA tests are required. - Issue type Bug means; there is a program error (bug) to be fixed. - Issue type Change Request means: Program should be changed in another way than just Bugfixing (e.g. features, configurations etc.) - Issue type Story is for agile boards only (e.g. Scrum); Story is a description of a feature that needs to be created or changed. - Issue type Epic is for agile boards only; Epic describes a group of related stories. c) Issue fields Main Fields: tallard JIRA first steps (2).docx 8/20
9 - Summary Summary can be either in English or German. Of course, if non-german speakers will be involved, everything should be in English. - Story Points Abstract measurement of complexity and size of a requirement. - Priority Self-explaining. Please also refer to Paragraph -d), Workflow actions. - Due Date Self-explaining. - Desired Delivery Date Self-explaining. - Description Describe your issue in details here. You may also enter another issue key here (e.g. AGNT- 23 ) which would result in a link to issue 23 of the AO_Agents project. - Components This field only appears in certain projects. It helps to specify which part of project is meant. In the above mentioned projects, the component selection is mandatory. In case you need to enter a new component, you need to create one first: o Click on Administration tab (see above, not the sign beside it) o Select the respective project o Under Components click on Add a new component - Assignee It s mandatory to enter a person here. If you don t know who it is, select Automatic here. - Config Enter yes, if issue contains a change request or bug that can be fixed only by a configuration change. It means that no new build is necessary. - Inquiry by This field only appear in certain projects. Select a country the issue either originally came from or is destined for. - Affects Version/s This field only appears in certain projects. In case the appropriate version is not listed there, you need to create an own one first: o Click on Administration tab (see above, not the sign beside it) o Select the respective project o Under Versions click on Show all or Add a version o Enter Version Name, Description and Release Date (if you know it) and click on Add Please refer also to 8.)) Versioning for rules and naming of versions and builds. - To be informed after creation Enter a JIRA user who will be informed automatically after issue is created. Note: It is not possible just to enter an address; user must be exist in JIRA first. - To be informed later / To be informed later 2 Enter a JIRA user who will be informed automatically after issue had been closed. Note: It is not possible just to enter an address; user must be exist in JIRA first. - Build No. This field only appears in a few projects. tallard JIRA first steps (2).docx 9/20
10 Please refer also to 8.)) Versioning for rules and naming of versions and builds. - Fix Version/s This field only appears in certain projects. In case the appropriate version is not listed there, you need to create an own one first: o Click on Administration tab (see above, not the sign beside it) o Select the respective project o Under Versions click on Show all or Add a version o Enter Version Name, Description and Release Date (if you know it) and click on Add Please refer also to 8.)) Versioning for rules and naming of versions and builds. - Steps to reproduce Self-explaining. Especially relevant for issue type bug. Additional Fields: - Epic / Theme Epics are issues that are too big to finish within one sprint. You should collect many stories in one Epic issue. In this case, you should enter for each user story an existing Epic issue key here. After you ve created e.g. an Epic and two Stories take a look at the Plan Board. Click on one of the Stories On the left side you get an overview of the Epic: tallard JIRA first steps (2).docx 10/20
11 - Flagged You may enter if an issue is marked as Impediment. - Attachment You may enter files here. You will also be able to paste a screenshot in JIRA however not here but in a next step: You need to create this issue first. Then go More Actions and then to Attach Screenshot in order to paste screenshot from clipboard. - Publication Range Similar to Due Date, but with free text (e.g. End of summer ) d) Notification There are two ways of notifications: In case you want to be informed yourself of a certain other issue, you can put it on a watch list: o Click on an issue (by clicking on issues before [not the sign beside it] and then by clicking on the link in column Key or Summary ) o Click on Watch : You will now be informed by about any changes on this issue. In case you want to have informed another user about an issue, just click on number in brackets to the right of Watch instead and you can select one out of a list. tallard JIRA first steps (2).docx 11/20
12 8.) Versioning (for developers only) Each program should display a full version number, containing program name, version number and build number, e.g. SPEEDonline Build 005 : a) Version number The AUTOonline syntax is as followed: YearOfRelease.VersionNumber (if there is no hotfix released yet) or YearOfRelease.VersionNumber.HotfixNumber (if there is at least one hotfix for that version). Examples: - Version means 2 nd regular release in year Version means second hotfix for first regular release in b) Build number The AUTOonline syntax is as followed: - Three-digit, with leading zeros, starts with Increases by one with each internal deployment. - However: After each new version number starts at 001 again! Examples: - Version has just been released with build number As soon as someone checks in code for version , build number falls down to 001 again. - However, if a hotfix has to be built, you have to check in for Build 005. tallard JIRA first steps (2).docx 12/20
13 9.) Agile Workflow (for developers only) b) Agile boards - Product Backlog / Priority of work (Scrum view): The priority of work is described by the positioning in the actual Scrum board. After an issue is moved from Backlog to an actual Sprint the product owner prioritizes the issues. The issue at top has the highest priority. In the Scrum Plan board you change the priority of an issue by click-and-hold the item with the mouse and move them to a higher position. In the Scrum workflow a developer always chooses the highest positioned issue and works on it. - Work view (without swimlanes): The image above displays a possible view of the Scrum board in Work mode (without so called swimlanes ). This view offers a maximum of overview. tallard JIRA first steps (2).docx 13/20
14 - Work view (with swimlanes): In another possible view (see picture above) swimlanes are activated. You see all issues in order of their priority and existing sub-tasks strictly assigned to the main issue. With this visualization all developers see which issue has the highest priority (that is not always clear in the view without swimlanes!) and which sub-tasks of a story belong to one issue. c) Workflow structure - Scrum workflow Summary: A new development request will be either moved from a JIRA start project (for AUTOonline: AO_Inbox ) to a Scrum project or directly created into a Scrum project. The product owner of Scrum prioritizes issues in the backlog of the Scrum Board (see 9.) d) Product Backlog / Priority of work (Scrum view): The priority of work is described by the positioning in the actual Scrum board. After an issue is moved from Backlog to an actual Sprint the product owner prioritizes the issues. The issue at top has the highest priority. In the Scrum Plan board you change the priority of an issue by click-and-hold the item with the mouse and move them to a higher position. In the Scrum workflow a developer always chooses the highest positioned issue and works on it. tallard JIRA first steps (2).docx 14/20
15 Work view (without swimlanes): for more details); issues with highest priority stand on upmost position. Signification of statuses: o Open (visible in column To Do ): Starting status for all new issues, usually assigned to product owner. If a developer moves an issue from Column To Do to In Work, status changes also to In Work. This indicates developer starts working on it. Developer becomes assignee automatically after status transition. o In Work (visible in column In Work ): Indicates that a developer works on that issue. Usually issues are called (user) stories and are typically divided into many sub-tasks (see 7.) b), Issue types for more information). Once developer has fixed a sub-task he moves it to column To Review and it becomes also status To Review. But if a developer moves a whole story from column In Work to To Review, status changes from In Work to Ready for QA. The different status names thus show that different actions have to follow: while single sub-tasks will be code-reviewed by another developer, stories need to be tested according to their requirements. o Ready for QA / To Review (visible in column To Review ): There are two different actions that could take place in column To Review : If a subtask has status To Review another developer has to code-review the issue. If a whole story has status Ready for QA a member of QA has to test the issue according the requirements. o In Test / In Review (visible in column In Test ): The code-review or the tests are executed in column In Test. After approval, stories will be moved to Done column; you have to choose between status Ready for Deployment or Closed. Sub-tasks will be moved to Done column, with status Closed. Please be aware: If you set an issue to Closed status without having deployed version first, a notification will be sent to the reporter of that issue. If that reporter do not belong to your company that would lead to irritation as they might think version would already have been published. o Ready for Deployment (visible in column Done ): This status only indicates that tests have been done, but deployment not yet. o Closed (visible in column Done ): Final status if issue has been realized (or cancelled). tallard JIRA first steps (2).docx 15/20
16 tallard JIRA first steps (2).docx 16/20
17 d) Workflow actions - Description of classic view: In JIRA, the most common view is Scrum view. But behind the visualization of Scrum all issues exists another view which we call classic view in this documentation. The classic view of an issue appears if you click on an issue in a Scrum board. It also may be a tool to change transitions and get an undetailed information on the priority of an issue. A user should normally use Scrum view but working with classic view is described as follows. - Transitions and Actions (classic view): Once you have selected a single issue (by clicking on issues before [not the sign beside it] and then by clicking on the link in column Key or Summary ), you will see a screen similar to this: Project / Project key Summary Causes no status change! Causes status change ( transition )! It is important to understand that you can perform a lot of actions in JIRA once you have selected a single issue. But only the right red-framed action group will cause a status change according to the workflow (usually Scrum workflow). You can see two Assign buttons on the example picture above, but the left one only changes the assignee and nothing else. The right button also changes the status from Open to In work. In JIRA only two transitions (actions with status change) will be displayed. If there are more you will find them by clicking on Workflow. - Priority of work (classic view): Two fields describe the priority of work: tallard JIRA first steps (2).docx 17/20
18 o Rank Field o Global Rank Note: There is still another priority field (just called priority or, shorter, only P ) which, however, AUTOonline doesn t use anymore as it only differs between Major, Minor etc. and does not make any difference between issues with the same e.g. high priority. A low ranking means this issue is more important than others. - Priority of work (agile boards): If you use agile Boards, issues with highest priority are displayed on top. - Transitions and Actions (agile board): Transition changes (from one status/column to another) are executed by click-and-hold an issue and drop it on a different column. Afterwards, issue is automatically assigned to you and for some transitions a window opens to insert further information. - Creation of own agile boards: Everyone is able to create his own scrum board. You only have to click on the sign beside Tools and click on Create board : There are two options: Kanban and Scrum. The main difference between these two board is that Kanban has no Sprints. A Kanban board is useful if you usually work without project due date rather than just a continuous work. Therefore it s recommended for e.g. support departments. After creation, you should configure your new board by clicking on the sign beside Tools and click on Create board : tallard JIRA first steps (2).docx 18/20
19 Here you have different options. You may change or edit your filter, add new columns or quick filters, etc. In this document the most common settings are described. You may set up your Scrum board as your wishes. For more information, please refer to official Greenhopper manual (agile development plugin for JIRA): In tab Columns we map the JIRA statuses (according to the picture below) to each column and (optionally) change Column Constraint to Issue Count, excluding sub-tasks : tallard JIRA first steps (2).docx 19/20
20 In tab Quick filters you are able to add (sub-)filters that display in the upper menu bar of the Scrum board in Work mode. You may create own quickfilters by using the JQL language. The preset filters are: In tab Estimation the view for the Burndown chart is determined. Options are None (only Story Points are shown) and Remaining Estimate and Time Spent. tallard JIRA first steps (2).docx 20/20
Inside JIRA scheme, everything can be configured, and it consists of. This section will guide you through JIRA Issue and it's types.
JIRA Tutorial What is JIRA? JIRA is a tool developed by Australian Company Atlassian. It is used for bug tracking, issue tracking, and project management. The name "JIRA" is actually inherited from the
More informationUse Guide STANDARD JIRA CLIENT. (Practical Case)
Use Guide STANDARD JIRA CLIENT (Practical Case) Version 3.0 Madrid, July 2018 1 OBJECTIVE 4 2 BASIC STANDARD SOLUTION 4 2.1 User Profiles 4 2.2 Types of issue 2.2.1 Functional Support 2.2.2 Corrective
More informationJetBrains YouTrack Comparison
JetBrains YouTrack Comparison YouTrack is an issue tracking tool by Jet- Brains. It is designed for development teams and serves as a one-stop shop for tracking daily tasks and bugs, planning sprints and
More informationUse Guide STANDARD JIRA-CLIENT ESTNDAR. Version 3.0. Standard JIRA Client Use Guide
Use Guide STANDARD JIRA-CLIENT ESTNDAR Version 3.0 Standard JIRA Client Use Guide Madrid, December, 2017 1 INTRODUCTION 3 2 JIRA CLIENT SOLUTIONS 4 3 INSTALLATION AND REQUIREMENTS 5 4 ACCESS 5 4.1 Request
More informationAtlassian JIRA Introduction to JIRA Issue and Project Tracking Software Tutorial 1
Atlassian JIRA Introduction to JIRA Issue and Project Tracking Software Tutorial 1 Once again, we are back with another tool tutorial. This time it s the Issue and Project Tracking Software Atlassian JIRA.
More informationWhat is JIRA? software development tool. planning and tracking the projects progress and supporting the team collaboration
Jakub Sykora What is JIRA? software development tool planning and tracking the projects progress and supporting the team collaboration supports both Agile (Scrum & Kanban) and waterfall methodologies What
More informationJira Quick Reference. User Manual (Jira 7.2)
Document Type: User Manual Prepared by: Uroš Arambašić Uros.arambasic@adacta.rs For: Adacta d.o.o. Trešnjinog cveta 11, 11000 Belgrade www.adacta.rs Version: 1.0 Date: Belgrade, 12. 04. 2017. Table of
More informationJIRA Overview & Configuration. Based on the A2F Framework
JIRA Overview & Configuration Based on the A2F Framework JIRA What is Jira? Proprietary issue tracking software tool Developed by Atlassian located in Sydney, Australia It provides Defect tracking Issue
More informationUser Manual. (Jira 7.2) Adacta d.o.o. Verovškova 55a, 1000 Ljubljana
Document Type: Prepared by: For: User Manual Project Managment Office BackOffice.PMOA@adacta.si Adacta d.o.o. Verovškova 55a, 1000 Ljubljana www.adacta.si Version: 1.0 Date: Ljubljana, 13. 4. 2017 Table
More informationJIRA MANUAL. Delaware Service Desk. Date: [20 June 2014] Version: 1.0
JIRA MANUAL Delaware Service Desk Date: [20 June 2014] Version: 1.0 Table of contents 1 Jira: how to use 5 1.1 Getting started 5 1.2 Navigation 5 1.2.1 Dashboard 1.2.2 Projects 5 7 1.2.3 Issues 1.2.4 Quick
More informationGetting Started with the Salesforce Agile Accelerator
Getting Started with the Salesforce Agile Accelerator Salesforce, Summer 16 @salesforcedocs Last updated: April 14, 2016 Copyright 2000 2016 salesforce.com, inc. All rights reserved. Salesforce is a registered
More informationTracking Issues with JIRA
Tracking Issues with JIRA Get a Linux Foundation Account JIRA User's Guide JIRA Setup for ONAP Viewing Issues in JIRA Reporting a Bug Proposing a New Feature JIRA Issue Types JIRA Workflow JIRA Statuses
More informationUSER GUIDE DATACOM JIRA ISSUES MANAGEMENT TUESDAY, 22 APRIL Version 1.1.0
USER GUIDE DATACOM JIRA ISSUES MANAGEMENT TUESDAY, 22 APRIL 2014 Version 1.1.0 Contents 1 INTRODUCTION... 3 2 KEY CONCEPTS TO UNDERSTAND... 4 2.1 Assigning vs. Progressing an Issue... 5 2.2 Workflow...
More informationPlorma Documentation. Release 0.4. Torsten Irländer
Plorma Documentation Release 0.4 Torsten Irländer November 11, 2015 Contents 1 Introduction 1 1.1 What is Plorma.............................................. 1 1.2 Licence..................................................
More informationUser Manual Version: 1.0.0
Template (Epic) Cloner for JIRA by Vilisoft Sp. z o.o. User Manual Version: 1.0.0 Index Release notes... 3 Introduction... 4 JIRA Administrator cases... 5 How to install... 5 How to configure... 5 New
More informationCustomer Helpdesk User Manual
Customer Helpdesk User Manual TABLE OF CONTENTS 1 INTRODUCTION... 3 2 HANDLING OF THE PROGRAM... 3 2.1 Preface... 3 2.2 Log In... 3 2.3 Reset Your Password... 4 2.4 Changing Personal Password... 4 3 PROGRAM
More informationThe Intuitive Jira Guide For Users (2018)
The Intuitive Jira Guide For Users (2018) idalko.com/jira-guide-pdf/ June 27, 2018 In this PDF you ll find the comprehensive Jira guide for users, brought to you by the Atlassian Platinum Solution Partner
More informationJIRA Studio Use Cases and Tutorial basis
JIRA Studio Use Cases and Tutorial basis Analysis of usefulness of JIRA Studio Eclipse tool-chain Tolga Tuncbilek, Elisa Kallio, Shiyuan Wang, Viktor Porvaznik Table of Contents 1 Introduction... 3 2 Data
More informationJira Connector Option - v18
Jira Connector Option - v18 Copyright 2019 ONEPOINT Projects GmbH. All rights reserved. ONEPOINT Projects, Enterprise Edition, Version 18 ONEPOINT Informationslosungen and the ONEPOINT Logo are registered
More informationServiceNow - Agile in ServiceNow
ServiceNow - Agile in ServiceNow The ServiceNow Agile Development application is an iterative and incremental process for software development environments. Agile Development application is enhanced with
More informationJIRA Standard Client. Objectives
JIRA Standard Client Objectives Introduction Standard JIRA Client Access User profiles Types of issue Functional Support Corrective Feature Request Big Feature Request Parameters and issues window of the
More informationPlugin Overview. So easy to use and a must have extension for any team. The Jira Tracking & Estimation plugin includes the following functionality:
Contents Plugin Overview... 2 Configuration... 5 Time Tracking (By Roles) Panel... 7 Assignee (By Roles) Panel... 9 Worklog (By Roles) Tab Panel... 10 Post Function... 11 Support... 13 Plugin Overview
More informationAgile Studio USER GUIDE 7.3
Agile Studio USER GUIDE 7.3 2017 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All other trademarks or
More informationAdministration Guide. Release
Administration Guide Release 13.3.00 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is for your informational
More informationPBWORKS - Student User Guide
PBWORKS - Student User Guide Spring and Fall 2011 PBworks - Student Users Guide This guide provides the basic information you need to get started with PBworks. If you don t find the help you need in this
More informationKanban One-Day Workshop
Kanban One-Day Workshop Copyright Net Objectives, Inc. All Rights Reserved 2 Copyright Net Objectives, Inc. All Rights Reserved 3 Lean for Executives Product Portfolio Management Business Product Owner
More informationThe Connector. Version 1.2 Microsoft Project to Atlassian JIRA Connectivity. User Manual
The Connector Version 1.2 Microsoft Project to Atlassian JIRA Connectivity User Manual Ecliptic Technologies, Inc. Copyright 2008 www.the-connector.com Page 1 of 86 Copyright and Disclaimer All rights
More informationSERVICE EXCELLENCE PROGRAM. Release Management Quick Reference Guide for users of ServiceNow. November 2013 THIS GUIDE BELONGS TO:
SERVICE EXCELLENCE PROGRAM Release Management Quick Reference Guide for users of ServiceNow November 2013 THIS GUIDE BELONGS TO: TABLE OF CONTENTS TABLE OF CONTENTS... 1 KEY RELEASE MANAGEMENT POLICIES
More informationAtlassian Confluence 5 Essentials
Atlassian Confluence 5 Essentials Stefan Kohler Chapter No. 5 "Collaborating in Confluence" In this package, you will find: A Biography of the author of the book A preview chapter from the book, Chapter
More informationThe Agile Samurai: How Agile Masters Deliver Great Software PDF
The Agile Samurai: How Agile Masters Deliver Great Software PDF Faced with a software project of epic proportions? Tired of over-committing and under-delivering? Enter the dojo of the agile samurai, where
More informationThis manual takes you through all the necessary steps to successfully setup your Hansoft JIRA integration.
Hansoft JIRA integration manual Top Next This manual takes you through all the necessary steps to successfully setup your Hansoft JIRA integration. Introduction Top Previous Next Hansoft/JIRA comparison
More informationConfluence User Training Guide
Confluence User Training Guide Below is a short overview of wikis and Confluence and a basic user training guide for completing common tasks in Confluence. This document outlines the basic features that
More informationVision, Roadmap, and Release Planning
Vision, Roadmap, and Release Planning Supplemental Materials for a Product Owner Jessica Komarek and Sara Alterisio 5 Levels of Agile Release Planning Vision Roadmap Release Iteration Daily What, Who,
More informationGETTING STARTED. Introduction to Backlog Grooming
GETTING STARTED Introduction to Backlog Grooming contents SECTION backlog grooming? SECTION 1 what is backlog grooming? 4 SECTION 2 who should be involved in a grooming session? 5 benefits of backlog grooming
More informationStory Refinement How to write and refine your stories so that your team can reach DONE by the end of your sprint!
+ Story Refinement How to write and refine your stories so that your team can reach DONE by the end of your sprint! Tonya McCaulley Director of Training ROME Agile + About Your Speaker Tonya McCaulley
More information/smlcodes /smlcodes /smlcodes JIRA. Small Codes. Programming Simplified. A SmlCodes.Com Small presentation. In Association with Idleposts.
/smlcodes /smlcodes /smlcodes JIRA T U T O R I A L Small Codes Programming Simplified A SmlCodes.Com Small presentation In Association with Idleposts.com For more tutorials & Articles visit SmlCodes.com
More informationChronodat Help Desk (Lite)
Chronodat Help Desk (Lite) (User Manual) By CHRONODAT, LLC For further information, visit us at www.chronodat.com For support, contact us at support@chronodat.com Version 2.0.0.0 Created: 10-03-2018 1
More informationChronodat Help Desk. (User Manual) By CHRONODAT, LLC
Chronodat Help Desk (User Manual) By CHRONODAT, LLC For further information, visit us at www.chronodat.com For support, contact us at support@chronodat.com Version 2.0.0.0 Created: 09-24-2018 1 P a g e
More informationHands-On Lab. Agile Planning and Portfolio Management with Team Foundation Server Lab version: Last updated: 11/25/2013
Hands-On Lab Agile Planning and Portfolio Management with Team Foundation Server 2013 Lab version: 12.0.21005.1 Last updated: 11/25/2013 CONTENTS OVERVIEW... 3 EXERCISE 1: AGILE PROJECT MANAGEMENT... 4
More informationChronodat Issue Tracker Add-in. User Manual CHRONODAT, LLC. February 15, 2017 Version P age
Chronodat Issue Tracker Add-in User Manual CHRONODAT, LLC February 15, 2017 Version 2.0 1 P age Introduction The introduction section of the document describes the scope and objective of Office 365 Chronodat
More informationAdopting Agile Practices
Adopting Agile Practices Ian Charlton Managing Consultant ReleasePoint Software Testing Solutions ANZTB SIGIST (Perth) 30 November 2010 Tonight s Agenda What is Agile? Why is Agile Important to Testers?
More informationGet Good at DevOps: Feature Flag Deployments with ASP.NET, WebAPI, & JavaScript
Visual Studio Live! Redmond 2016 Get Good at DevOps: Feature Flag Deployments with ASP.NET, WebAPI, & JavaScript Benjamin Day www.benday.com Benjamin Day Brookline, MA Consultant, Coach, & Trainer Microsoft
More informationSpiraTest Quick Start Guide Inflectra Corporation
SpiraTest Quick Start Guide Inflectra Corporation Date: January 28, 2018 Contents Introduction 2 1. Logging In and Selecting a Project 3 2. Define the Requirements 5 3. Create the Release and Iteration
More informationOpenProject AdminGuide
OpenProject AdminGuide I. Contents I. Contents... 1 II. List of figures... 2 1 Administration... 2 1.1 Manage projects...2 1.2 Manage users...5 1.3 Manage groups...11 1.4 Manage roles and permissions...13
More informationAgile Software Development. Software Development Methodologies. Who am I? Waterfall. John York JOHN YORK EECS 441 FALL 2017 A BRIEF LOOK
Who am I? John York Agile Software Development JOHN YORK Director of Engineering at ProQuest Dialog Chief Technologist SpellBound AR A Computer Engineer from the University of Michigan! An agile development
More informationInformation Package for Reviewers
Information Package for Reviewers Author: Customer Care Team Date of publication: April 2014 Latest update: June 2015 Table of contents 1 Introduction A. Document purpose B. Compatible browsers with review.cogen.com
More information1. Installing R4E 1. 1) Provision Software Sites 2. 2) Install Version Control System Features 3. 3) Install R4E feature 4. 4) Install Versions
R4E Documentation 1. Installing R4E 1. 1) Provision Software Sites 2. 2) Install Version Control System Features 3. 3) Install R4E feature 4. 4) Install Versions Connectors 2. Getting Started 1. Overview
More informationTARGETPROCESS JIRA INTEGRATION GUIDE
TARGETPROCESS JIRA INTEGRATION GUIDE v.2.10 JIRA Integration Guide This document describes JIRA plugin configuration. 1 JIRA INTEGRATION OVERVIEW... 2 CONFIGURE TARGETPROCESS JIRA INTEGRATION PLUGIN...
More informationUSER MANUAL. Inprowiser Engineering
USER MANUAL Capacity Tracker for JIRA Cloud Inprowiser Engineering 1 Contents Introduction... 2 Installation and pre-requisites... 3 Installation... 3 Pre-requisites... 4 Get started with Capacity Tracker...
More informationTABLE OF CONTENTS INTRODUCTION...3 MAIN ELEMENTS OF A PRODUCT ROADMAP...4 PRODUCT ROADMAPS...11 MARKETING ROADMAPS...27 ABOUT PRODUCTPLAN...
TABLE OF CONTENTS INTRODUCTION...3 MAIN ELEMENTS OF A PRODUCT ROADMAP...4 PRODUCT ROADMAPS...11 Product Roadmap Template... 12 Agile Roadmap Template... 13 Release Plan Template... 14 Portfolio Roadmap
More informationProject Management Framework
Project Management Framework Release Notes Version 7.1.1 Framework Overview The Project Management Framework (PMF) is a powerful Project Management application designed for the management of Scrum projects.
More informationSpecifying Acceptance Criteria
Freelance SQL Server Consultant Specifying Acceptance Criteria I have worked with some agile product owners who when the write user stories, the like to go epic on the acceptance criteria, in fact when
More informationSAFe Atlassian Style (Updated version with SAFe 4.5) Whitepapers & Handouts
SAFe Atlassian Style (Updated version with SAFe 4.5) Whitepapers & Handouts Exported on 09/12/2017 1 Table of Contents 1 Table of Contents...2 2 Abstract...4 3 Who uses SAFe and Why?...5 4 Understanding
More informationPlacement Administration and Support System (PASS) User Guide. System Version January 2018 (v9)
Placement Administration and Support System (PASS) User Guide System Version 2.0 22 January 2018 (v9) Placement Administration and Support System (PASS) User Guide System Version 2.0 22 January 2018 Contents
More informationCon o t n i t n i e n n e t n a t l a S u S p u p p l p ier e r P or o t r a t l User Manual
Continental Supplier Portal User Manual Continental Supplier Portal Manual Continental AG, 14.05. 2 Contents 1. Process description... 3 2. Log in on Continental Supplier Portal... 4 2.1 First view...
More informationAHAU SOFTWARE. User Guide. Easy Projects Outlook Add-in. version 2.6
AHAU SOFTWARE User Guide Easy Projects Outlook Add-in version 2.6 This Outlook add-in makes it possible to sync tasks, import contacts and calendar, as well as to get quick access to attachments and messages
More informationActivityTimeline User Guide https://activitytimeline.com
ActivityTimeline User Guide https://activitytimeline.com Copyright 2018 ActivityTimeline Contents 1. Getting Started... 3 1.1 Overview... 3 1.2 Logging In and Out... 3 1.3 Dashboard Overview... 4 1.4 Issues
More informationActivityTimeline User Guide
ActivityTimeline User Guide https://activitytimeline.com Copyright 2018 ActivityTimeline Contents 1. Getting Started... 3 1.1 Overview... 3 1.2 Logging In and Out... 3 1.3 Dashboard Overview... 5 1.4 Header
More informationOnboarding checklist. 1. Understand Asana
Onboarding checklist Asana is the easiest way for teams to track their work and get results. If you re joining a team that s already using Asana, this onboarding checklist will get you up to speed. We
More informationUSER GUIDE MyLinedata / JIRA
USER GUIDE MyLinedata / JIRA Users_Documentation_JIRA.docx 1/20 This documentation, or any part of the information herein, may not be modified without the prior consent of Linedata. Such representation
More informationCONFIGURING SAFE V4.0 IN THE IBM COLLABORATIVE LIFECYCLE MANAGEMENT
CONFIGURING SAFE V4.0 IN THE IBM COLLABORATIVE LIFECYCLE MANAGEMENT Abstract In this document, we provide step-by-step guidance to configure support for the SAFe V4.0 methodology in CLM tooling. Amy Silberbauer
More informationInstructions on how to approve invoices in Hogia Approval Manager
Hogia Performance Management AB Instructions on how to approve invoices in Hogia Approval Manager The new Approval web is a HTML5 application. Its appearance is slightly different from the previous Silverlight
More informationPega Agile Studio USER GUIDE 7.4
Pega Agile Studio USER GUIDE 7.4 2018 Pegasystems Inc., Cambridge, MA All rights reserved. Trademarks For Pegasystems Inc. trademarks and registered trademarks, all rights reserved. All other trademarks
More informationPBWORKS - Student User Guide
PBWORKS - Student User Guide Fall 2009 PBworks - Student Users Guide This guide provides the basic information you need to get started with PBworks. If you don t find the help you need in this guide, please
More informationEQUELLA Workflow Moderation Guide
Helping put innovation into education EQUELLA Workflow Moderation Guide Version 6.5 MELBOURNE - CANBERRA - HOBART 1800 EDALEX - www. edalexsolutions.com ABN 56 611 448 394 Document History Date Change
More informationFacebook Page Insights
Facebook Product Guide for Facebook Page owners Businesses will be better in a connected world. That s why we connect 845M people and their friends to the things they care about, using social technologies
More informationAgile Software Development. Software Development Methodologies. Who am I? Waterfall. John York JOHN YORK EECS 441 WINTER 2018 A BRIEF LOOK
Agile Software Development JOHN YORK EECS 441 WINTER 2018 John York Director of Engineering at ProQuest Dialog Chief Technologist SpellBound AR A Computer Engineer from the University of Michigan! An agile
More informationOmni-Channel for Administrators
Omni-Channel for Administrators Salesforce, Winter 18 @salesforcedocs Last updated: November 2, 2017 Copyright 2000 2017 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark of
More informationLive Agent for Support Agents
Live Agent for Support Agents Salesforce, Winter 18 @salesforcedocs Last updated: November 30, 2017 Copyright 2000 2017 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark of
More informationOmni-Channel for Administrators
Omni-Channel for Administrators Salesforce, Summer 18 @salesforcedocs Last updated: August 16, 2018 Copyright 2000 2018 salesforce.com, inc. All rights reserved. Salesforce is a registered trademark of
More informationSpidertracks Website User Guide
Version 7.1.0 4 May 2016 Spidertracks Website User Guide For using the Spidertracks Go website and additional information. 1 Table of Contents 1. Website Architecture 2. Create a User Account 3. Creating
More informationWeb4BIS User Guide Version 3.3
Web4BIS User Guide Version 3.3 WEB4BIS User Guide - Table of Contents Table of Contents 1. Login and Logout in WEB4BIS... 3 2. Administration... 4 2.1. Change User Data... 4 2.1.1 Change Person Information...
More informationUser Stories. Wednesday, January 23, 13
User Stories 1 User Stories and their friends: Use Cases, Scenarios, Personas, Gherkins and Kanbans 7 W s Who writes user stories? What is a user story? When is it written? Where are they seen? Why is
More informationUser Manual - Contractors
www.gfi.be www.gfi.be User Manual - Contractors Contractors Portal Total Created for: Total Date: 23/03/2015 Version: 1.1 1. Document Management Revision history Version Date Object Updated by 1.0 06/02/2015
More informationThe Connector Version 2.0 Microsoft Project to Atlassian JIRA Connectivity
The Connector Version 2.0 Microsoft Project to Atlassian JIRA Connectivity User Manual Ecliptic Technologies, Inc. Copyright 2011 Page 1 of 99 What is The Connector? The Connector is a Microsoft Project
More informationRelease Notes. Release
Release Notes Release 13.3.00 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is for your informational
More informationIntroduction. User Privileges. PEPFAR SharePoint: Poweruser Guide
PEPFAR SharePoint: Poweruser Guide Introduction Welcome to your role as a Poweruser of a PEPFAR SharePoint site! This guide will give you an overview of your roles and responsibilities in maintaining the
More informationDevelopment Processes Agile Adaptive Planning. Stefan Sobek
Development Processes Agile Adaptive Planning Stefan Sobek Agile Planning Process Adaptive Planning In agile projects frequently issues and changes will be discovered. Go into these projects with expectations
More informationNPS Apps - Google Docs Facilitated by Liza Zandonella Newtown High School May, 2013
NPS Apps - Google Docs Facilitated by Liza Zandonella Newtown High School May, 2013 Creating, Uploading and Sharing Documents To open Google Docs, select Drive on the menu bar of your Google Mail browser.
More informationDocumentation. Structure Plugin for JIRA
Documentation Structure Plugin for JIRA Exported on 08/28/2017 1 Table of Contents 1 Table of Contents...2 2 Structure User's Guide...17 2.1 Basic Concepts...17 2.1.1 Default Structure... 18 2.1.2 Favorite
More informationCOMPANY SETTINGS A MANUAL
COMPANY SETTINGS A MANUAL Introduction If you are the first of your organization to register for the messenger, you will automatically be the company admin. If you do not have admin rights, another company
More informationArcMap Online Tutorial Sarah Pierce How to map in ArcMap Online using the Fresh Prince of Bel Air as an example
Fall GARP ArcMap Online Tutorial Sarah Pierce How to map in ArcMap Online using the Fresh Prince of Bel Air as an example Westfield State University Let s say you ve never used ArcGIS before and your professor
More informationWeb Site Documentation Eugene School District 4J
Eugene School District 4J Using this Documentation Revision 1.3 1. Instruction step-by-step. The left column contains the simple how-to steps. Over here on the right is the color commentary offered to
More informationUser Guide Version March Copyright Perfony
User Guide 1.13.0 Version March 2016 Copyright Perfony 2015-2020 Your Perfony user guide This user guide is here to help you navigate through the key features of your iperfony space. For more details,
More informationGetting Started Guide
Getting Started Guide New to ActiveBuilding? This guide will provide five quick steps that you will need to effectively use your new portal. We will cover the basics: Signing in as a new staff user Adding/removing
More informationAn Intro to Scrum. Agile (Iterative) Project Development. Written in 2001 Can be read in its entirety at:
An Intro to Scrum Agile (Iterative) Project Development Broken down into iterations Self-Managed Minimal Planning Easily/Quickly adapts to change The Agile Manifesto Written in 2001 Can be read in its
More informationCase Management Digital Service Sprint Review Sprint 5.1: 11/16/17 11/29/17. CWDS / Child Welfare Digital Services
Case Management Digital Service Sprint Review Sprint 5.1: 11/16/17 11/29/17 CWDS / Child Welfare Digital Services Agenda Sprint Stories Core County Brief Sprint Backlog and Team Metrics Feature Based Presentations:
More informationJIRA, Confluence and their integration
Term work report JIRA, Confluence and their integration Průmyslové informační systémy(a0m33pis) Prepared by Radu Fiser Czech Technical University in Prague Faculty of Electrical Engineering Summer semester
More information<Partner Name> <Partner Product> RSA ARCHER GRC Platform Implementation Guide. Swimlane 2.x
RSA ARCHER GRC Platform Implementation Guide Jeffrey Carlson, RSA Partner Engineering Last Modified: 11/02/2017 Solution Summary The RSA Archer integration allows Swimlane
More informationkalmstrom.com Business Solutions
Kanban Task Manager for Outlook Manual Table of contents 1 INTRODUCTION...3 1.1 LANGUAGES...4 1.2 REQUIREMENTS...4 1.3 SYSTEMS...4 2 INSTALLATION OF KANBAN TASK MANAGER...6 2.1 INTRODUCTION...6 2.2 PROCESS...6
More informationGetting Started with the DEFEND System
Getting Started with the DEFEND System DEFEND (DRI Employee Field trip Emergency Notification Delivery) is a system which automatically notifies individuals when DRI researchers, working in the field,
More informationProduct Backlog Document Template and Example
Product Backlog Document Template and Example Introduction 1. Client Information (Name(s), Business, Location, contact information) 2. Team Information Team Member Names (contact information) 3. Project
More informationMonitoring and Evaluation Tool
Monitoring and Evaluation Tool USER MANUAL March, 2014 www.menarid.icarda.org THIS PAGE LEFT EMPTY INTENTIONALLY USER MANUAL Definitions and abbreviations Chart... Graphical representation of M&E project
More informationThe Improvement Backlog. Claude Rémillard InCycle Software
The Improvement Backlog Claude Rémillard InCycle Software So, you are managing a software development organization? Agile adoption New tools and practices Source: http://choicebookkeeping.com.au/2011/03/business-changes-a-foot/
More informationHarePoint Analytics. For SharePoint. User Manual
HarePoint Analytics For SharePoint User Manual HarePoint Analytics for SharePoint 2013 product version: 15.5 HarePoint Analytics for SharePoint 2016 product version: 16.0 04/27/2017 2 Introduction HarePoint.Com
More informationKanban & Making Your Production Scream
Kanban & Making Your Production Scream Presented by Clinton Keith Clinton Keith Takeaway Provide you with another set of tools for production Demonstrate how Kanban is being used successfully today in
More informationCAT4.14 User Manual -Application-
CAT4.14 User Manual -Application- Last Updated 2017/08/31 About trademark System names and product names described in this manual, including the registered trademarks and trademarks of other companies
More informationTWS Caller v3.1 User Guide
TWS Caller v3.1 User Guide 2008 Algoria. TWS (Telephony Web Services) and associated products, is a registered trademark Contacts and Support ALGORIA Address: Tel: Fax: E-mail: URL: 3, rue Verte 95100
More informationAtlas 2.0. Atlas Help
Atlas 2.0 Atlas Help Borland Software Corporation 700 King Farm Blvd, Suite 400 Rockville, MD 20850 Copyright Micro Focus 2015. All rights reserved. Portions Copyright 1998-2009 Borland Software Corporation
More informationGetting Started A GUIDE FOR TEAM MEMBERS
Getting Started A GUIDE FOR TEAM MEMBERS What is CxAlloy Total Quality? 1 User Expectations 1 Your Account 1 Accessing the Site 2 Navigating CxAlloy TQ 2 Updating Issues 4 Uploading Files 5 Completing
More information