SAFe Atlassian Style (Updated version with SAFe 4.5)

Transcription

1 SAFe Atlassian Style (Updated versin with SAFe 4.5)

2 Table f Cntents 1 Abstract Wh uses SAFe and Why? Understanding SAFe Why Des it Matter? Implementatin f SAFe within the Atlassian Suite Blended Perspectives' Cnfiguratin and Slutin New Update - SAFe Cnclusin Table f Cntents 2

3 Authrs: Miles Faulkner, C-CEO and Majken Cnnr, Senir Cnsultant 1 Abstract Objective This paper aims t better the reader's understanding f Scaled Agile's SAFe methdlgy and its implementatin with the Atlassian Suite. In additin t enriching the reader's understanding f SAFe, this paper will als explre Blended Perspectives' take n SAFe and what slutins we have t ffer. We use a specific set f tls when it cmes t ur implementatin and cnfiguratin f SAFe. In additin we discuss what's new in SAFe 4.5. It's imprtant t nte that Blended Perspectives take an agnstic psitin n methdlgies but will always identify prs and cns based n ur implementatin experience. Abut Blended Perspectives Blended Perspectives is an Atlassian Platinum Enterprise certified Slutins partner. We are a Canadian federally incrprated specialist cnsulting firm, perating ut f Trnt, Canada, with ffices als lcated in New Yrk, USA. Blended Perspectives specializes in cnsulting fr infrmatin systems that drive cllabratin, innvatin and prductivity; ur slutins encmpass strategy, prcesses and culture fr intranets and tracking. Our missin is t enable Crpratins t unleash the pwer f their teams and t leverage the true ptential f their business via enhanced tls and prcesses. 2 Wh uses SAFe and Why? SAFe is a framewrk fr entire rganizatins that wish t scale Agile t achieve Enterprise level strategic and peratinal bjectives. It caters t stakehlders thrughut the rganizatin, crdinating artifacts and wrkstreams. It prvides cmmn language and principles that can be scaled apprpriately t keep all levels f yur rganizatin aligned. SAFe 4.5 intrduces multiple framewrk diagrams t chse frm depending n the size f yur enterprise. SAFe is tls agnstic: it prescribes bjectives and hw they hang tgether, withut recmmending specific implementatin tls. If yu are reading ur whitepaper yu prbably are interested in implementing SAFe using Atlassian tls. 3 Understanding SAFe On the surface, SAFe can lk like a difficult t understand and cmplicated, multilayered methdlgy. Scaled Agile prvides varius artifacts and definitins, describing a "freely revealed knwledge base f prven success patterns fr implementing Lean-Agile sftware and systems at enterprise scale" (SAFe website) but what des this all mean? This is where we want t break SAFe dwn int its mst basic elements, and nce we understand these elements we can delve deeper int why this all matters. S, where d we start? SAFe 4.0 is a framewrk fr an entire rganizatin, perating n up t fur levels: prtfli, value stream (ptinal), prgram, and team. Start by examining the prtfli level. This level can be thught f as the tp f the pyramid f an imaginary enterprise. Frm this level cmes the prjects and directin in which the cmpany wishes t mve. These are als the peple and prcesses needed t mve the cmpany frward and create slutins driving a business clser t its bjective (SAFe website). This is essentially the executive level. The prtfli is made up f elements such as the value streams. Abstract 3

4 Next, the value streams level. While this level is intended fr "builders f large and cmplex slutins", it is still imprtant t have an understanding f this level n matter the size f yur rganizatin (SAFe website). This level is ptinal in SAFe 4.0 and is generally recmmended fr larger enterprises. In simple terms, the value stream level helps with budgeting as well as an understanding f financial bundaries fr larger prjects (SAFe website). Next the prgram level. Essentially, the prgram level hlds a large team, cmprised f many small teams which we will describe in further detail in the team level sectin. This team f teams wrks twards an verarching prject, executed thrugh prgram increments (essentially a plan fr each team f teams). Prgram increments are then made up f 5 iteratins, 4 iteratins f wrk n the prduct r slutin and the last iteratin is devted t innvatin and preparatin fr any imprtant architectural wrk fr the next increment (SAFe website). This "team f teams" fllws a set rutine fr the iteratins starting with planning, executing, reviewing, and ending with sme reflectin fr imprvement. A Prject Manager is in charge f the cntent fr the prgram increments, as well as the team backlg. Finally this entire prcess is verseen by a Release Train Engineer. Nw we will further explre the teams that make up this team f teams (SAFe website). At the team level, there is a similar prcess t that f a standard scrum. Agile teams wrk tgether and deliver iteratins n a bi-weekly basis. A Prduct Owner is tasked with deciding and delegating cntent fr the iteratins, in additin t being in charge f the team backlg. Teams fllw a set rutine fr the iteratins starting with planning, executing, reviewing, and ending with sme reflectin fr imprvement (SAFe vide). Understanding SAFe 4

5 All f these elements cme tgether t create SAFe: Fr a mre visual descriptin, check ut this vide: SAFe 4.0 in 5 minutes 4 Why Des it Matter? Nw that we've explained hw SAFe wrks and brken it dwn int its cmpnents we can begin t understand why use SAFe and when it is mst useful what des it aim t imprve? In a nutshell, SAFe assists businesses tackle challenges assciated with creating and eventually delivering tp quality enterprise class sftware within a reasnable timeframe. SAFe is a structured scaled mdel fr Agile teams t build functinality twards larger functinal areas such as web platfrms and ther cmplex systems. As we knw, Agile is an excellent way t rganize, cmmunicate and prblem slve as an individual, team, and rganizatin. In fact, the Agile methdlgy is naturally hw many individuals think and slve issues. Peple tend t wrk better when they are trusted, have autnmy t slve prblems, and wrk as a team. Agile helps prmte and blend the values f individuals int a team culture. The Agile methdlgy priritizes certain values, which can be difficult fr the enterprise that desn't necessarily share the same set f pririties. This is where SAFe cmes in. The Scaled Agile Framewrk brings everything tgether by essentially creating ne big team, driving twards the agreed enterprise bjectives. SAFe has teams grup tgether t create teams f teams which band tgether t ensure the successfulness f the Agile methdlgy and efficiency f rganizatins using it. Figuring ut hw t scale Agile is f great imprtance t enterprises, which is why Why Des it Matter? 5

6 SAFe has becme a ppular methd used by enterprises lking t becme mre Agile. This brings us t Atlassian's healthy inventry f pwerful tls that can wrk hand-in-hand with the SAFe methdlgy. It shuld be nted hwer that SAFe hierarchies are nly as strng as their cmpnent pieces and s the fundatins f best practices Agile delivery must be in place. This can be a struggle since this alne is nt easy. 5 Implementatin f SAFe within the Atlassian Suite The Atlassian Suite prvides the ideal tl set when it cmes t the implementatin f SAFe in any enterprise. We use JIRA plus Prtfli fr JIRA in ur implementatins f SAFe. In terms f JIRA, we custmize at the prject level, twards SAFe - it is the prject that the teams belng t and this that hld their wrk. It als allws individuals t have apprpriate Kanban n Scrum bards depending n their SAFe level as discussed abve. JIRA's flexibility allws fr different issue types within the same prject t have different wrkflws, allwing fr the implementatin f Safe's Kanban bards exactly t spec. JIRA als has tight integratins with cding tls and cntinuus dev tls which is useful fr any enterprise. Furthermre, JIRA extends transparency all the way int cde, thrugh t Bamb fr deplyments and back t Cnfluence fr requirements. Prtfli fr JIRA hlds the hierarchy between the "artifacts" and prvides a tp-dwn view f yur rganizatin. Prtfli als allws crss prduct releases t allw agile teams t wrk twards the same prgram increments frm within their wn prjects. We als use Cnfluence fr dcumentatin as it is a useful and imprtant tl t ensure alignment and applicatin dcumentatin. Anther Atlassian tl which can be useful when paired with SAFe is HipChat and Stride. These tls allw fr real time distributed cnversatins - which are f great imprtance t enterprises. 6 Blended Perspectives' Cnfiguratin and Slutin Our first step is t tackle terminlgy and the mapping f SAFe t JIRA bjects such as issue types. A bit mre n SAFe terminlgy: SAFe terminlgy JIRA/JIRA Prtfli functinality We riginally tk the apprach t make every identifiable bject r level in SAFe a Prtfli hierarchy level. Hwever we believe nt everything identified in the list belw shuld be a hierarchy level in Prtfli. Our current apprach is t nly reflect the Issue hierarchy as Prtfli hierarchies, e.g. Stries make up Features, and Features make up Capabilities etc. Thereafter, the SAFe levels are represented thrugh JIRA Prjects and their assciated Bards. Prtfli level Created related issue type Reflected as a JIRA prject with cnfiguratin specific t Prtfli level wrk Prtfli Epics Created Hierarchy level and related issue type These live in Prtfli type JIRA prjects Value Stream level Created related issue type Lives in the Prtfli prject that the Value stream belngs t Reflected as a JIRA prject with cnfiguratin specific t Value Stream level wrk Value Stream Epics Created Hierarchy level and related issue type Implementatin f SAFe within the Atlassian Suite 6

7 These live in Value Stream type JIRA prjects Capabilities Created Hierarchy level and related issue type These live in Prtfli type JIRA prjects Prgram Level Created related issue type Lives in the Value Stream prject that the Prgram belngs t Reflected as a JIRA prject with cnfiguratin specific t Prgram level wrk Prgram Stream Epics Created Hierarchy level and related issue type These live in Prgram type JIRA prjects Features Created Hierarchy level and related issue typethese live in Prgram type JIRA prjects Others have used JIRA's built in Epic issue type fr this when implementing SAFe, hwever this is nt currently ur recmmendatin ARTs (Release Trains) Grup f teams assigned t the Prgram in Prtfli Teams Create Prtfli Teams t reflect each team Stries Already exist in JIRA JIRA/JIRA Prtfli functinality SAFe terminlgy Themes Mapped t Capabilities Stages and Skills Cnfigured frm the Reprts view Added as functinality fr identifying and planning teams within ARTs Blended Perspectives' Cnfiguratin and Slutin 7

8 Belw is a diagram illustrating hw we tackle SAFe implementatin and cnfiguratin: We believe that Prtfli fr JIRA is a valuable asset when it cmes t SAFe's implementatin and cnfiguratin. We make use f Prtfli fr JIRA in a number f ways. Each level has a specific prject type. Belw we will illustrate these prject types and the issue types that accmpany them: Template Prtfli Level Prject Issue Type Scheme: Prtfli Level Issue Type Scheme Prtfli Epic Value Stream Template Value Stream Level Prject Issue Type Scheme: Value Stream Level Issue Type Scheme Value Stream Epic Capability Prgram Template Prgram Level Prject Issue Type Scheme: Prgram Level Issue Type Scheme Prgram Epic Blended Perspectives' Cnfiguratin and Slutin 8

9 Feature Stry Bug Epic Task Sub-task Custm Fields Add "Prject" type custm field called "Value Stream Prject" t "Value Stream" screen Add "Prject" type custm field called "Prgram Prject" t "Prgram" screen Add "Parent Link" field t all issue types in the hierarchy: Value Stream Epic, Capability, Prgram Epic, Feature, Epic This shws the Prtfli parent when viewing the JIRA issue in the JIRA prject Child issues shw up by default 7 New Update - SAFe 4.5 While much f the abve descriptins and explanatins still stand, there have been a number f changes t SAFe after the intrductin f SAFe 4.5. T begin with let us tuch n what is different. Firstly, we ntice that in SAFe 4.5, "value stream" has been changed t "large slutin". While this nly matters when cnsidering the implementatin f Full SAFe (Smething which is discussed in further detail belw), it is nnetheless a ntable difference. Nw a lk at what's new. Accrding t the SAFe Website, changes intrduced in SAFe 4.5 fall int the fllwing categries: 1. Essential SAFe and Cnfigurability 2. Innvatin with Lean Startup and Lean UX 3. Scalable DevOps and cntinuus delivery 4. Implementatin radmap 5. Other imprtant stuff With SAFe 4.5 rganizatins can nw chse which f the fur new cnfiguratins best suit their needs: Full SAFe, Prtfli SAFe. Large Slutin SAFe, and Essential SAFe (SAFe website). Each f these cnfiguratins has a different number f levels, starting with the basics and mving twards Full SAFe (see diagram belw). Secnd n the list we have innvatin with Lean Startup and Lean UX. This is new cntent that has been added t SAFe's Lean Startup Cycle. Lean Prtfli Management and Lean Budgets will assist rganizatins with rapid innvatin and implementatin. Next we have scalable DevOps and cntinuus delivery. This new additin will help "accelerate the build-measure-learn cycle that supprts faster innvatin and mre frequent releases." The all new radmap is made up f a clickable "interactive graphic linked t a 12-article series that describes the majr activities that have prven t be effective in successfully implementing SAFe." (SAFe website) Given these changes and additins, we will be adding new prject types and als change terminlgy such as changing value stream t large slutin. Full SAFe: New Update - SAFe 4.5 9

10 8 Cnclusin The Scaled Agile Framewrk (SAFe) is a ppular methd t essentially allw any rganizatin f any size t scale Agile teams. This is especially imprtant fr large rganizatins and enterprises wh may find it mre difficult t becme agile due t their massive scale, hwever values the benefits f the Agile Methdlgy. The Atlassian Suite wrks particularly well with SAFe and is f great use when implementing SAFe in any rganizatin because its s flexible. With each tl prviding a different benefit, Atlassian tls are the ideal set that cmpliment any implementatin f SAFe. With ur experienced team, we, at Blended Perspectives, can help yu nt nly better understand the imprtance f ging agile, but als the implementatin f SAFe and the Atlassian Suite. Cntact us fr mre infrmatin n SAFe r anything Atlassian! References SAFe 4.0 in 5 minutes Cnclusin 10