JIRA Software: SAFe
Objective
How to setup JIRA Software for enterprise customers? / How to implement SAFe in JIRA Software?
Environment
Server
Procedure
By scaling agile framework in JIRA Software, it becomes easy to plan work across multiple teams, track the overall progress of the team and useful in analysis and planning phases.
The SAFe framework discusses three levels of planning: portfolio level, program level, and team level. Each level has its own items for tracking: needs on the portfolio level, epics on program level and stories on the team level.
- Portfolio level: In this level, portfolio items are managed according to a portfolio management process or project portfolio management process. This process needs to be reflected in a workflow that is assigned to the portfolio issue types and the portfolio project. You can visualize this workflow with a Kanban board which is ideal for tracking the progress of the portfolio items.
- Program level: A JIRA project in this level can contain epics, stories, tasks (e.g. refactor task or design task), and sub-tasks. Epics typically belong to a system or a business service. Therefore, the JIRA projects on the program level should follow this enterprise architecture of systems or services.
- Team level: Here, the scrum teams plan their sprints with stories, tasks, and other work items. Teams in one level are not “stand alone,” but part of the bigger picture and part of the entire process.
Refer the blog for detail information on scaling agile in the enterprise with SAFe and JIRA Software and white paper for scaling agile with our Atlassian and SAFe for teams.
Last modified on Dec 23, 2016
Powered by Confluence and Scroll Viewport.