Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Jimi Wikman

New SAFe® 5.0 Introduction White Paper

Recommended Posts

Quote

This white paper provides an overview of SAFe 5.0, the Big Picture graphic, the seven core competencies, and the values, mindset, principles, and practices that guide teams to more effectively build solutions in a far leaner—and more Agile—fashion.

You can use the new white paper in a couple of different ways: As an initial level of education for leaders, managers, and executives to help them reach the tipping point for SAFe adoption, and inspire them to learn more in a Leading SAFe® class To prepare students in the basics of SAFe prior to taking a course (e.g., Implementing SAFe® with SPC certification, Leading SAFe®, etc.)

https://www.scaledagileframework.com/blog/new-safe-5-0-introduction-white-paper/

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Similar Content

    • By ©Jimi Wikman
      Jira tool manager with the task of stabilizing the system and setting up work processes for all teams within H&M. Responsible for several projects including cloud initiatives and coordination with other systems such as ServiceNow. Heavily involved in designing the build processes (requirements, development, design, deploy and test) for the process office. Responsible for the design and implementation of SAFe in Jira and the build processes. Responsible for a small team of Atlassian experts. Supported 400+ teams with Jira questions and training of work processes.
    • By + Magnus Lindblom
      Entrepreneur, business developer and manager with experiences from radically improving test organisations and starting, operating and selling restaurant businesses.

      Specialties: Business and organizational development. Strategic test management in complex environments such as in banking and insurance.
    • By ©Jimi Wikman
      BigPicture 7 introducerar en av de bästa Program Boards för PI Planning med visuella beroende jag har sett. Det är bara en av de många nya features som BigPicture 7 presenterar och som vi kan se under våren 2019.
      BigPicture från SoftwarePlant har länge varit ett av de bästa alternativen till Jiras egna Portfolio for Jira och med BigPicture 7 så tycker jag att de tar klivet upp till en topp position för projekt portfolio plugins för Jira. Det är framförallt deras visuella board för program nivå som saknas i andra produkter, men det finns en hel del annat smått och gott också.


      BigPicture 6 hade en fantastisk översikt och även om man lägger till en ny vy så finns den gamla vyn kvar också. Personligen älskar jag den gamla vyn som för mig är en perfekt blandning av tidsplanering och översikt över det som utvecklas. Den nya vyn i BigPicture 7 är anpassad till SAFe.

       
      Scope Module ger en bra översikt och det enda som jag kan känna kan förbättras är själva trädstrukturen och listningen av issue types. Jag föredrar layouten som Portfolio for Jira har där issue types och trädstrukturen sitter ihop. Det ger för mig en enklare och tydligare översikt över strukturen och nedbrytningen.

      För mig så har BigPicture 7 den överlägset bästa översikten över resurser och kompetenser. Det är enkelt och lättöverskådligt att se vart det fattas kompetenser och resurser. Med funktionen att mappa in kompetenser i Jira ärendena direkt får du rätt översikt (nästan) alltid. Det gör också att det blir mer naturligt att bryta ner ärenden så det blir rätt typ av aktiviteter.

       
      Board 2.0

       
      BigPicture 7 kommer med en ny board, fast den följer samma fantastiska layout som i BigPicture 6. Nytt är att den nya boarden är anpassad för just PI Planning enligt SAFe standard. Det här är en vy som ofta efterfrågas och som saknas stort i Jira idag. Det här är för mig den stora säljpunkten för BigPicture 7 för den här funktionen är verkligen spot on som man säger.
      Gant Chart 2.0

       
      Alla älskar en bra Gant Chart och BigPicture har alltid haft en av de bästa för Jira. I BigPicture 7 så introducerar man två nya funktioner som efterfrågats av kunderna: Live Sync och Sandbox.
      Live sync är egentligen lite missvisande för det handlar om kollaborativ editing. Nu kan flera användare jobba samtidigt utan att riskera att förstöra något för de andra. Du behöver inte längre trycka på uppdatera och hoppas att ingen annan gjort något som ställer till det. Nu ser du allting när det händer. Ungefär som collaborative editing i Confluence med andra ord.
      Sandbox låter dig experimentera med din planering utan att påverka den aktiva planen. Du kan göra olika scenarion och sedan implementera den du gillade bäst när du så önskar. Det gör det möjligt att direkt se hur olika förändringar slår på olika områden utan att du behöver oroa dig för att det ska påverka den aktiva planeringen. Ett ovärderligt verktyg för att hantera oplanerade ändringar med andra ord.
      BigPicture 7 kommer under våren 2019 och senare under 2019 kommer BigPicture 7.5 som innehåller Portfolio Management Module som ger Full Safe i BigPicture. Du kan läsa mer om detta och detaljerna för BigPicture 7 på SoftwarePlants hemsida.
      Personligen tycker jag att detta är den största om mest intressanta uppdateringen bland Jira plugins hittils under 2018. BigPicture 7 ser ut att bli en stor hit under 2019 och jag kommer självklart att skriva mer om det så fort jag vet mer eller har haft möjlighet att prova på. Ganska troligt att BigPicture 7 kommer att bli ett ämne för Atlassian User Group Stockholm också under 2019.
      Vad tycker du om BigPicture 7 av vad du ser här och hur gillar du BigPicture 6 om du använt det?
    • By + David Samuelsson
      Specialties: Development Environments, Eclipse and ecosystem, Clearcase, Clearquest,Quality Center, build systems, Symbian tool chain, Team leading, Management leading. Management of Open source tools/software in corporate environments.
    • By ©Jimi Wikman
      SAFe 5.0 can be previewed on a preview section of the Scaled Agile For Enterprise website. The suggested changes takes several steps forward towards a lean organization type of frame work. With that comes challenges for companies who see SAFe as a development framework and not an organization one. Will this make it easier or harder to have organizations adapt to SAFe?
      In SAFe for Lean Enterprises 5.0 comes with two new competencies and updated to five competencies. It also pushes pretty hard towards the business side with new business agility and SAFe for business teams. The biggest change is probably the merge of the teams level and the program level into one single level called Essential. While it is good to involve business more and I agree with the arguments for merging team and program levels I fear that this will make SAFe less attractive. That is because now it require a complete transformation of the company, while before you could have it living along side other frameworks.
       

       
      New Focus on Business Agility
      "Business Agility is the ability to compete and thrive in the digital age by quickly responding to market changes and emerging opportunities with innovative business solutions. It requires that everyone involved in delivering solutions—business and technology leaders, development, IT operations, legal, marketing, finance, support, compliance, security, and others—use Lean and Agile practices to continually deliver innovative, high-quality products and services faster than the competition."
      This sounds amazing, but I would say that less than 1% of all enterprise companies are even close to having a lean approach to their organization. Almost all companies have some areas, but as a whole I would say almost every enterprise company still have a waterfall and project based approach to their organization.

       
      Continuous Learning Culture New
      "The Continuous Learning Culture competency describes a set of values and practices that encourage individuals—and the enterprise as a whole—to continually increase knowledge, competence, performance, and innovation. This culture is achieved by becoming a learning organization, committing to relentless improvement, and promoting a culture of innovation."
      This is where I think many organizations dedicated to implement SAFe will get uncomfortable. Continuous learning cost a lot of money. We are talking several millions a year and a dedicated workforce for coaching and educating the organization. In most of the companies I have see this is very uncommon. Most if the time there is a small central team and then a multitude of initiatives throughout the organization that is not very structured or large enough to support everyone.
      I would love to see this implemented, but the cost for it will surely give a lot of resistance.

       
      Organizational Agility New
      "The Organizational Agility competency describes how Lean-thinking people and Agile teams optimize their business processes, evolve strategy with clear and decisive new commitments, and quickly adapt the organization as needed to capitalize on new opportunities."
      This makes sense, unless you consider that most enterprise companies are not Lean-thinking in their mindset and the sheer complexity of their operations makes Lean-thinking difficult. Again most companies still struggle with Agile where it mostly become an Ad-hoc stress trap due to poor adaptation and support.
      Again this require a huge commitment with an almost total organization transformation. The cost alone is monumental and the effort to move your entire organization, as well as changing the tool set, towards this goal makes it a big obstacle towards a SAFe implementation for many companies. If they can afford the cost and can see the change management through however this would be very interesting indeed. I know of no company today that works this way on an organization level and I am not sure it is even possible at an enterprise company.

       
      Team and Technical Agility Restructured
      "The Team and Technical Agility competency describes the critical skills and Lean-Agile principles and practices that high-performing Agile teams and Teams of Agile teams use to create high-quality solutions for their customers. The result is increased productivity, better quality, faster time-to-market, and predictable delivery of value."
      This description has been updated, but unfortunately it still does not define teams as product based. It also does not give any focus towards work satisfaction or team health, which is important factors to consider as some teams should not use an Agile methodology as it is damaging to their health. Not really much news here other than some updates to to the merge of team and program level.

       
      Agile Product Delivery   Restructured
      "The Agile Product Delivery competency is a customer-centric approach to defining, building, and releasing a continuous flow of valuable products and services to customers and users. This competency enables the organization to provide solutions that delight customers, lower development costs, reduce risk, and outmaneuver the competition. The DevOps and Release on Demand competency has been renamed to Agile Product Delivery."
      Again not much news here. Some additional emphasis on customer centric design thinking, which is a bit amusing as most organizations are very far from customer centric in general and still very new to the concept of design thinking. Hopefully this will increase the demand for UX and CRO as user testing and A/B testing is a rather rare occurrence in today's enterprises. On the DevOps side I still do not see this working, even after 10 years of "implementation" on many organizations. In fact the trend is to separate dev and ops more than uniting them...

       
      Lean Portfolio Management   Restructured
      "The Lean Portfolio Management competency aligns strategy and execution by applying Lean and systems thinking approaches to strategy and investment funding, Agile portfolio operations, and governance. These collaborations give the enterprise the ability to align strategy to execution, to meet existing commitments reliably, and to better enable innovation."
      This is the one thing I wish every enterprise organization would focus on right now. In to many organizations there are barely any strategic portfolios and contracts are all written as fixed price engagements that kill any chance of agility. There are few, if any, enterprise architects and overall the structure and control on portfolio levels are pretty bad. Not much news here, but an improved description and a slight alignment towards organization agility.

       
      Enterprise Solution Delivery   Restructured
      "The Enterprise Solution Delivery competency describes how to apply Lean-Agile principles and practices to the specification, development, deployment, operation, and evolution of the world’s largest and most sophisticated software applications, networks, and cyber-physical systems. The Business Solutions and Lean Systems Engineering competency has been renamed to Agile Product Delivery"
      This section has been rewritten and again aligned a bit with the merge of teams and program. It still promote a microservices solution and continuous deliver system that is not really aligned with the complexity of large scale system development with multiple teams of different cadence. Despite that this is a good section with many good descriptions that would make life easier if followed.

       
       
      Lean-Agile Leadership  Restructured
      "The Lean-Agile Leadership competency describes how Lean-Agile Leaders drive and sustain organizational change by empowering individuals and teams to reach their highest potential. They do this through leading by example, adopting a Lean-Agile mindset, and lead the change to a new way of working. The result is more engaged employees, increased productivity and innovation, and successful organizational change."
      This section is updated and rewritten a bit. The SAFe implementation roadmap has been updated a bit as well with 2 new courses. One for Lean Portfolio Management and one for Agile Product and Solution Management (APSM)

       
      Overall these are good changes, but I fear that the extent of the new changes can make organizations feel that SAFe is becoming increasingly difficult to implement. On the other hand it can also be the leverage certain part of the organization need to push the change that they see is necessary. It also makes it more attractive from a strategic perspective to have a framework that will actually transform all aspects of the organization.
      So there are some good things and some, potentially, bad things in SAFe 5.0.
      I like it, how about you?
       
×
×
  • Create New...