Category
Courses

Search

Trending blog posts

Understanding the SAFe® Program Dependency Board Retrospective

The Program Increment (PI) Planning is a key differentiator event, unique to the SAFe® way of working. It is a 2-day (2.5 to 3 days in case of Distributed environments) planning event at the beginning of each PI where all the members of the Agile Release Train(ART), Leadership, Business and other stakeholders gather to plan for the next upcoming PI. The PI objectives and the Program Board are the two major outcomes of this large-scale Planning Event. This article delves into the Program Board creation, template, uses and the benefits it brings to the smooth planning and running of the upcoming PI. What is a SAFe® Program Board? The SAFe Program Board is created by teams at the time of PI Planning to visibly represent dependencies of their features with other teams in the Agile Release Train (ART). It also represents how the feature completion dates fare against any milestone events. This visual radiator helps to quickly sort out major dependency issues and fix the chronological order of execution to meet the major milestones at the time of PI Planning. It is recommended to be used after the PI Planning as well, so that emerging and evolving changes are updated, and teams respond accordingly.What Is Found on a SAFe® Program Board?  A typical SAFe Program Board is a row and column matrix that consists of the following: List of Teams: The list of teams that are part of the ART and the supporting teams which work with all the teams in the ART such as UX, Architecture etc. are listed as rows in a matrix. Iterations: All the Iterations that will be part of the PI appear as columns of the Matrix board. The Iterations can be 2 or 3 weeks long and so the number of Iterations depends on cadence set for the iterations in the ART. So, there can be 3 or 4 iterations with an IP(Innovation & Planning) iteration at the end. Milestones/Events: The first row in the Matrix lists any Milestone event that is about to happen during the course of the PI; for e.g Trade show, a compliance SLA with one of the Customers, or an Engineering Milestone like a technological upgrade. This ensures to give visibility on whether the features related to that event have been planned to be completed before the milestone or not. Features: Each of the teams places the Feature card at the Iteration at which it is planned to be completed. For e.g if Team X plans to work on a Feature A with 4 stories, 3 planned for Iteration 1 and 1 planned for Iteration 2 , the Feature A will appear only once as a blue card in the matrix at Iteration 2. This is because the Feature is complete only at the end of Iteration 2. Dependencies: If Team X is dependent on the Shared UX Team and Team Y to complete Feature A in Iteration 2, the dependencies are marked as a Red card in the Iterations at which the UX Team and Team Y work on the dependencies. There is a red coloured connector between the Feature A Card and all the dependency Red Cards. What are the uses of a SAFe® program board?  The Program Board makes it obvious if there is a risk of missing an important milestone or if the dependencies do not make sense chronologically.  It is a very important Visual Information Radiator that is created and used in PI Planning and also during the course of PI. For e.g, Team Y is delivering Feature B very close to the Milestone Event which is a risk. Team Z is delivering Feature C after the Milestone event which must be replanned. Team X is Planning to complete Feature A in Iteration 2. It has dependencies with the UX Team and Team Y. But Team Y is planning to work on the dependent story in the same Iteration 2. Team Y can replan to work on it in Iteration 1 because Feature A is high priority and cannot risk missing completion because of an important milestone. Deeper learning from the program dependency board  Other than the obvious benefits of the Program board, it also exposes certain other facets of planning at scale. It could quickly point out if any team(s) is completing too many features at the very end of the PI. From the Sample Program board, we can infer Team X is only completing features at the end of the PI. Teams that have dependencies with multiple teams might become a bottle neck for the progress of other teams. Team Z has dependency with almost all the teams in the ART. Ways must be devised during the PI Planning itself to reduce this sort of dependency. The board might expose that one Team is having a lot of features tied to different Milestones. The priority of work seems not equally distributed amongst the teams. The shared services teams like Architecture, UX, Infrastructure etc, will have a clear picture on how other teams are dependent on them and how to prioritize the request from these teams. If there is a milestone very close to the beginning of Iteration 1, the senior Management and Business teams can anticipate a risk of not meeting this milestone.   How to set up your SAFe® program board  The following are the basic inputs required for the Program Board: Milestone dates come from the Product Management or Business Teams. Any Engineering Milestone dates come from the Engineering Head. The list of the teams in the ART and the Shared Services teams are input by the RTE The names to be used for the teams in the board should be provided by Scrum Master in consultation with teams. Once the input information is available, the RTE creates the Board before the PI Planning starts. Scrum Masters start populating the board for their respective teams in consultation with their teams during the course of the PI Planning.When to use a SAFe® program board  The Program Board is created and very useful at the time of PI Planning. During PI Planning the board is reviewed at intervals and at draft reviews, and changes are incorporated. It is highly recommended to keep the board up to date throughout the PI to add and modify emerging dependencies and changing milestones. The Program Board can be reviewed and updated at the ART level meetings by the Scrum Masters and RTE, so that the latest information is available on the board. Create your own SAFe® program board  The program board can be created as a virtual board in the case of distributed teams. There are tools like Miro that can be used to create Virtual program boards.  In the case of co-located teams, a physical board can be displayed at a common area where all teams and shared teams can have access to it. Different coloured cards must be used such as– blue for Feature Cards, Red for Dependency and Red Strings for connecting the Feature card to their dependencies. It is better to have a soft board as the base so that board pins can be used to hold the connector strings in place.Good Practices and Tips for Program Board Efficiency  The Program Board used well serves as a very effective visual information radiator and planning aid for all stakeholders at PI Planning and during the PI execution.  Having all the necessary information like the Milestone events before the PI Planning can ensure that the most up to date information goes into the Program board at the time of PI. Awareness of the Milestone can help Business and Teams prioritize and plan the features. For features not tied to a Milestone, Business Teams get an indication of when Features are likely to be completed. This helps them to plan the release of these features.  The Shared Service teams (UX, Infrastructure, Architecture etc) can prioritize and plan their work according to the dependencies and milestones on the board. The RTE can take the responsibility of bringing the Program Board as a topic of conversation at ART synch meetings, so that the Scrum Masters and other stakeholders can keep it current and updated and the ART can benefit from it. Through the Program Board the RTEs can track and communicate the various dependencies and milestone targets to all the relevant stakeholders to constantly get their attention and support as required. The teams can check in to the board any point of time to get a view of the larger context of the release e.g features worked on by other teams and their target completion. There are likely to be changes to the plans drawn out during PI. In keeping with the Agile Principles of embracing and responding well to change, the Program board can be revisited every week and kept updated. All said, the Program Board should not replace the constant collaboration and interaction amongst the teams and stakeholders but a tool that provides context and serves as an aid to the communication. SAFe® Program Board Template  A SAFe Program Board Template can be created using a sample board described by SAFe. You can find out more about it here. Miro also has a free template that can be used. ConclusionThe Program Board is one of the most major outcomes from the PI Planning event and one of the most important tools that can be used by the RTE and Scrum Masters during the PI execution phase. It is an important Visual Radiator for running Agile in a Scaled environment and can be used effectively and efficiently for best results. 
Understanding the SAFe® Program Dependency Board Retrospective
Radhika
Radhika

Radhika Subramoniam

author

The author is an Agile Consultant working in the areas of process consultation and Agile coaching and transformation. She has been part of the software product development industry spanning field service, fleet management, telecom billing and network management. 

Posts by Radhika Subramoniam

Understanding the SAFe® Program Dependency Board Retrospective

The Program Increment (PI) Planning is a key differentiator event, unique to the SAFe® way of working. It is a 2-day (2.5 to 3 days in case of Distributed environments) planning event at the beginning of each PI where all the members of the Agile Release Train(ART), Leadership, Business and other stakeholders gather to plan for the next upcoming PI. The PI objectives and the Program Board are the two major outcomes of this large-scale Planning Event. This article delves into the Program Board creation, template, uses and the benefits it brings to the smooth planning and running of the upcoming PI. What is a SAFe® Program Board? The SAFe Program Board is created by teams at the time of PI Planning to visibly represent dependencies of their features with other teams in the Agile Release Train (ART). It also represents how the feature completion dates fare against any milestone events. This visual radiator helps to quickly sort out major dependency issues and fix the chronological order of execution to meet the major milestones at the time of PI Planning. It is recommended to be used after the PI Planning as well, so that emerging and evolving changes are updated, and teams respond accordingly.What Is Found on a SAFe® Program Board?  A typical SAFe Program Board is a row and column matrix that consists of the following: List of Teams: The list of teams that are part of the ART and the supporting teams which work with all the teams in the ART such as UX, Architecture etc. are listed as rows in a matrix. Iterations: All the Iterations that will be part of the PI appear as columns of the Matrix board. The Iterations can be 2 or 3 weeks long and so the number of Iterations depends on cadence set for the iterations in the ART. So, there can be 3 or 4 iterations with an IP(Innovation & Planning) iteration at the end. Milestones/Events: The first row in the Matrix lists any Milestone event that is about to happen during the course of the PI; for e.g Trade show, a compliance SLA with one of the Customers, or an Engineering Milestone like a technological upgrade. This ensures to give visibility on whether the features related to that event have been planned to be completed before the milestone or not. Features: Each of the teams places the Feature card at the Iteration at which it is planned to be completed. For e.g if Team X plans to work on a Feature A with 4 stories, 3 planned for Iteration 1 and 1 planned for Iteration 2 , the Feature A will appear only once as a blue card in the matrix at Iteration 2. This is because the Feature is complete only at the end of Iteration 2. Dependencies: If Team X is dependent on the Shared UX Team and Team Y to complete Feature A in Iteration 2, the dependencies are marked as a Red card in the Iterations at which the UX Team and Team Y work on the dependencies. There is a red coloured connector between the Feature A Card and all the dependency Red Cards. What are the uses of a SAFe® program board?  The Program Board makes it obvious if there is a risk of missing an important milestone or if the dependencies do not make sense chronologically.  It is a very important Visual Information Radiator that is created and used in PI Planning and also during the course of PI. For e.g, Team Y is delivering Feature B very close to the Milestone Event which is a risk. Team Z is delivering Feature C after the Milestone event which must be replanned. Team X is Planning to complete Feature A in Iteration 2. It has dependencies with the UX Team and Team Y. But Team Y is planning to work on the dependent story in the same Iteration 2. Team Y can replan to work on it in Iteration 1 because Feature A is high priority and cannot risk missing completion because of an important milestone. Deeper learning from the program dependency board  Other than the obvious benefits of the Program board, it also exposes certain other facets of planning at scale. It could quickly point out if any team(s) is completing too many features at the very end of the PI. From the Sample Program board, we can infer Team X is only completing features at the end of the PI. Teams that have dependencies with multiple teams might become a bottle neck for the progress of other teams. Team Z has dependency with almost all the teams in the ART. Ways must be devised during the PI Planning itself to reduce this sort of dependency. The board might expose that one Team is having a lot of features tied to different Milestones. The priority of work seems not equally distributed amongst the teams. The shared services teams like Architecture, UX, Infrastructure etc, will have a clear picture on how other teams are dependent on them and how to prioritize the request from these teams. If there is a milestone very close to the beginning of Iteration 1, the senior Management and Business teams can anticipate a risk of not meeting this milestone.   How to set up your SAFe® program board  The following are the basic inputs required for the Program Board: Milestone dates come from the Product Management or Business Teams. Any Engineering Milestone dates come from the Engineering Head. The list of the teams in the ART and the Shared Services teams are input by the RTE The names to be used for the teams in the board should be provided by Scrum Master in consultation with teams. Once the input information is available, the RTE creates the Board before the PI Planning starts. Scrum Masters start populating the board for their respective teams in consultation with their teams during the course of the PI Planning.When to use a SAFe® program board  The Program Board is created and very useful at the time of PI Planning. During PI Planning the board is reviewed at intervals and at draft reviews, and changes are incorporated. It is highly recommended to keep the board up to date throughout the PI to add and modify emerging dependencies and changing milestones. The Program Board can be reviewed and updated at the ART level meetings by the Scrum Masters and RTE, so that the latest information is available on the board. Create your own SAFe® program board  The program board can be created as a virtual board in the case of distributed teams. There are tools like Miro that can be used to create Virtual program boards.  In the case of co-located teams, a physical board can be displayed at a common area where all teams and shared teams can have access to it. Different coloured cards must be used such as– blue for Feature Cards, Red for Dependency and Red Strings for connecting the Feature card to their dependencies. It is better to have a soft board as the base so that board pins can be used to hold the connector strings in place.Good Practices and Tips for Program Board Efficiency  The Program Board used well serves as a very effective visual information radiator and planning aid for all stakeholders at PI Planning and during the PI execution.  Having all the necessary information like the Milestone events before the PI Planning can ensure that the most up to date information goes into the Program board at the time of PI. Awareness of the Milestone can help Business and Teams prioritize and plan the features. For features not tied to a Milestone, Business Teams get an indication of when Features are likely to be completed. This helps them to plan the release of these features.  The Shared Service teams (UX, Infrastructure, Architecture etc) can prioritize and plan their work according to the dependencies and milestones on the board. The RTE can take the responsibility of bringing the Program Board as a topic of conversation at ART synch meetings, so that the Scrum Masters and other stakeholders can keep it current and updated and the ART can benefit from it. Through the Program Board the RTEs can track and communicate the various dependencies and milestone targets to all the relevant stakeholders to constantly get their attention and support as required. The teams can check in to the board any point of time to get a view of the larger context of the release e.g features worked on by other teams and their target completion. There are likely to be changes to the plans drawn out during PI. In keeping with the Agile Principles of embracing and responding well to change, the Program board can be revisited every week and kept updated. All said, the Program Board should not replace the constant collaboration and interaction amongst the teams and stakeholders but a tool that provides context and serves as an aid to the communication. SAFe® Program Board Template  A SAFe Program Board Template can be created using a sample board described by SAFe. You can find out more about it here. Miro also has a free template that can be used. ConclusionThe Program Board is one of the most major outcomes from the PI Planning event and one of the most important tools that can be used by the RTE and Scrum Masters during the PI execution phase. It is an important Visual Radiator for running Agile in a Scaled environment and can be used effectively and efficiently for best results. 
Understanding the SAFe® Program Dependency Board Retrospective
Blogs
5687
Understanding the SAFe® Program Dependency Boa...

The Program Increment (PI) Planning is a key dif... Read More

Is a SAFe® Agilist Course Right for You?

Companies adopting SAFe® have found huge benefits with its implementation.  But what is SAFe and how is it connected to Agile? This article is your introduction into the world of SAFe and on one of the most popular courses in SAFe – the Leading SAFe Course, SAFE Agilist Certification.Getting started with ScrumMany companies start their Agile journey with the most popular Agile framework i.e Scrum.  It is a simple methodology that lays down guidelines and practices - Scrum Ceremonies, Scrum Values and Scrum Roles in order to achieve the Agile Values and Principles.To start with, in an organization, a few Business Units/Divisions start practicing Scrum for a few teams. Once they realize the benefits of Agile and Scrum they would want to extend the same to multiple teams and multiple Business Units/Divisions.But, would a simple “Scrum of Scrums” methodology that worked wonders for small teams, work well for huge Enterprises with multiple Businesses and teams spread across the globe? Will it be possible, in the process of this transformation, to satisfy the others who are in this mix including Technology Partners, Vendors and Suppliers, evolving Customer demands and Competition? Probably not. And that is where a framework that is meant for large Enterprises to practice Agile at Scale becomes the need of the hour.What exactly is SAFe?SAFe is a Scaled Agile Framework that lays down proven principles, guidelines and practices to be followed by enterprises to achieve Business Agility. The latest version, SAFe 5, is built around Seven Core Competencies that enable Enterprises to become customer-centric and respond to changing market conditions and emerging technologies.Seven Core Competencies of SAFe 5Lean Portfolio Management – Creating a portfolio vision, roadmap, strategy and optimizing operations to align strategy, funding and execution,Organizational Agility – Bringing the entire organization (Marketing, Finance, Legal, HR teams) within the ambit of a Lean Agile Mindset. Organizing development efforts around value, creating dual Operating system of “network and traditional” hierarchies within the organization to encourage innovative start up culture along with Enterprise Stability.Continuous Learning Culture – Promoting Continuous Learning, Improvement and Innovation.Lean Agile Leadership – Leaders exhibiting the desired Agile behaviours they wish to see in their teams.Team and Technical Agility – Cross functional Business and Technical teams that deliver with Quality.Agile Product Delivery – Customer centric solutions on a continuous delivery pipeline, developing on cadence and releasing on demand.Enterprise Solution Delivery – Lean product delivery integrating the complete solution ecosystem- Partners, Suppliers and Vendors.SAFe recommends different flavours of the framework depending on the practicing organization’s needs and where they stand in their Agile journey.The four flavours of SAFe 5 areEssential – Basic configuration of the framework that recommends the foundational elements - roles, practices and competencies to be successful with SAFe.Solution – Additional roles, practices and competencies required to build large scale applications, large Solutions and networks.Portfolio – Provides the framework for Portfolio Strategy, investment funding aligning portfolio strategy with execution. A simple Portfolio configuration includes the Essential configuration.Full – Comprehensive configuration of the framework covering Essential, Solution and Portfolio.Why is SAFe important for individual practitioners?  For an employee who is part of an organization that has chosen to adopt SAFe, it is important that he/she is aware of the framework at large, the current state of the organization and where they are headed in the future. The first step for an individual would be to acquire the knowledge about SAFe in general and then delve deep into the areas which are closest to his/her area of expertise.  Depending on the employee’s role and responsibilities, he/she could take up the most appropriate SAFe Course and choose to get Certified in the same. Some of the courses are listed below. Leading SAFe , Certified SAFe Agilist: For leaders and executives to acquire a Lean-Agile mindset and propagate and develop the same across the organization. Implementing SAFe, Certified SAFe Program Consultant:  For change agents and Agile coaches who are spearheading the implementation of SAFe in the organization. SAFe for Teams, Certified Agile Practitioner: For team members. It can also serve as a foundational course for all employees. SAFe Scrum Master, Certified SAFe Scrum Master  SAFe Advanced Scrum Master, Certified SAFe  Advanced Scrum Master SAFe Product Owner/Product Manager, Certified SAFe Product Owner/Product Manager SAFe Release Train Engineer, Certified SAFe RTE: For SAFe RTEs to enhance their skills as servant leader and coach of a Release Train. There are also other courses specific to Government, Architects, DevOps, Portfolio Management etc. Why should I choose SAFe Agilist? If an organization has decided to adopt SAFe and begin the transformation journey then the SAFe Agilist Course is the right place to begin with. Executives, thought Leaders like Enterprise Architects or Department Heads, Program Managers, Project Managers, and Employee Managers who are major stakeholders of large-scale transformations will find this course apt.  The SAFe Agilist course, in fact, is the number one step in the SAFe implementation roadmap. Before a SAFe Transformation, the Leaders, Executives and Managers of the organization should truly believe in the Lean-Agile principles and themselves start exhibiting the Lean Agile behaviours and mindset, which they wish to see in their teams. They should know the approach to be taken to go agile at the team, department and organizational level.   By becoming SAFe Agilists, the Leaders become one of the front-runners of Agile in the organization and are able to wield the necessary influence needed to transform their teams. Lean Agile leadership is the foundational competency that is part of every flavour of the SAFe framework, reiterating how important it is to have Lean Agile Leadership at the helm to implement SAFe  successfully. If in case, your organization has not yet started the SAFe journey and is on the threshold of a tipping point it would be wise to become a SAFe Agilist. A Certified SAFe Agilist and Leader becomes a valuable asset for the organization that is about to begin its Agile journey. You could become one of the core Visionary members driving and implementing the SAFe Agile transformation.If not intended for the scenarios mentioned above, the SAFe Agilist certification also proves to be career progression path for many servant leaders.What is the learning objective of SAFe Agilist?  Explore SAFe Principles derived from Lean and Agile philosophies of Product Development Becoming Lean Agile Leaders in order to exhibit and propagate the Lean Agile mindset throughout the Organization Establishing Team and Technical Agility Agile Product Delivery by adopting a customer-centric mindset, organizing around value, applying Design and Systems Thinking. Experiencing a PI Planning Event. The PI Planning is one of the trademark SAFe events with immense benefits. Experiencing a mock PI Planning event during the course helps the Business Leaders to understand the significance of such an event and the benefits it brings to the organization. Building a Continuous Delivery Pipeline and instilling a DevOps culture. Exploring Lean Portfolio Management and its Implementation in the organization. Establishing Business Agility by aligning the Applications and Solutions Implementation to the Portfolio Strategy. The Leading SAFe Certification Completion of the SAFe Agilist course gives access to the exam and all related study materials as part of a Learning Plan in the SAFe Community Platform. The Learning Plan helps the individual to prepare for the Certification exam through Mock test and Practice Questionnaires. Details of the Certification exam can be found here. On successful completion of the exam, apart from the SAFe Agilist PDF certificate and SAFe Agilist digital badge there is   One-year membership to the SAFe Community Platform, which includes access to the SA Community of Practice Access to Meetup groups and events that connect you with other SAFe certified professionals A variety of learning resources to support you during your SAFe journey What is the target audience and the eligibility criteria for SAFe certification?  Typically, the target audience for the SAFe Agilist course are people in Executive, Managerial and Leadership roles in Enterprise Organizations. They might be part of a set of Visionary leaders initiating and spearheading a SAFe transformation or an important stakeholder in the Agile Release Train who needs to get onboarded into the SAFe way of working. As per Scaled Agile, Inc, prerequisites are highly recommended for those who intend to take the SAFe® 5 Agilist (SA) Certification exam.  5+ years’ experience in software development, testing, business analysis, product, or project management Experience in ScrumConclusionThe Scaled Agile Framework has become an important proven methodology of practicing Agile at scale. More and more enterprises are kicking off their SAFe transformation journeys, and for those who are already running SAFe , they are drawing out implementation plans to sustain and upgrade. At the foundation of these large transformations and upgrades are the Lean Agile Leaders who are responsible for driving the change through the length and breadth of the organization. Being a Certified SAFe Agilist is definitely a very credible achievement and opens doors for exciting opportunities in the Agile world. 
Is a SAFe® Agilist Course Right for You?
Blogs
9604
Is a SAFe® Agilist Course Right for You?

Companies adopting SAFe® have found huge benefits... Read More

What Is ScrumXP and How Does It Compare With Other Agile Frameworks

This article briefly talks about popular Agile methodologies Scrum and XP, and how both these frameworks have been merged into ScrumXP—giving you the best of both worlds!  Scrum Scrum is the leading Agile framework practiced in the industry today. It follows an iterative approach where development cycles are 2 /3/4 weeks long. At the end of every iteration an incremental version of the product/solution is ready to be shipped.  Scrum prescribes events / ceremonies and specific roles within the team in order to achieve alignment and agility.  Sprint Ceremonies /Events Sprint Planning at the start of the Sprint Daily Stand-up during the Sprint Sprint Demo and Review to showcase the incremental working software developed in the iteration Sprint Retrospective at the end of the Sprint Scrum Roles Product Owner – Responsible for the product that is being developed. Is the representative of the Customer and Business. Scrum Master – Facilitates and orchestrates the various Scrum events, guides the team to align with Scrum values and principles. Team Member – Focusses on achieving Sprint goals, continuously strives to improve. Scrum Values  Courage - Every team member feels safe to fail and learn, to seek help, to say ‘no’ and question something that is going wrong. Commitment – Commits to Sprint goals as a team. Does not overcommit.  Focus - Aims to complete what is started and steer away from distractions and unprioritized/ "shoulder tap" work. Limits Work in Progress. Openness - Seeks and values feedback and opportunities to learn. Makes impediments, failures and learnings visible. Respect - Team collaborates and acknowledges the work and achievements of every member. Builds trust. Extreme Programming (XP) XP is one of the earliest ,most successful and proven Agile Methodologies.  It is very specific regarding the practices to be followed. XP is recommended to be used when the Customer is fully committed to deep involvement with the development team. XP teams rapidly produce software in short(mostly one week) iterations taking immediate feedback from the Customer. XP Values Communication – Communication within the team is as important as communication with the Customer Simplicity - Building a system that is easy to revise and maintain. Trying not to engineer too many and too much and only do what is required at that time. Feedback – Continuously striving to obtain feedback and acting on the feedback from Customer, Team and the Product. Courage – Courage to persevere and do the right thing. Respect – Respect for fellow team members and all stakeholders. XP Core Practices XP mandates certain core Engineering practices that distinguish this Agile methodology from the others. These practices take care of different aspects of agility and are interconnected at the same time.  They are grouped as below. Fine scale feedbackWhole TeamAll the contributors to a project – Developers, Testers, Analysts, Coaches etc who are part of the Project are part of the “Whole Team” that is centered around the Customer.Planning GameThe Customer presents the desired features and lays out an initial plan for the project. XP teams revise the release plan regularly.During Iteration Planning, the Customer presents the features desired for the next two weeks. XP teams build software in two-week “iterations”, delivering running, useful software at the end of each iteration.The total involvement by the Customer during Planning is an important practice of XP.Pair ProgrammingAll production code is touched by two team members. This ensures there is already another “reviewer” at work as the code is getting produced. This practice largely avoids bugs and coding errors.Test Driven DevelopmentTest before code is religiously practiced. Before a single line of code is written, a test for the same has to be written and run. This immediate and short feedback loop immensely helps to avoid waste, like bugs and wrong code.Customer TestsAcceptance Tests are defined by the Customer to validate if the features that are being introduced are fit to the purpose. The team automates these tests and builds a suite of such tests to run whenever required and to get immediate feedback from the system to check if all is well.Continuous processContinuous IntegrationContinuously integrating the code avoids the major problems that creep up when it is done  just before the release. Testing on a fully integrated system helps to detect critical bugs that might otherwise stay undetected for long.Design ImprovementDesign Improvements and Refactoring happens at healthy intervals to ensure system is cohesive and loosely coupled. This ensures the system can be easily extended with new features, scaled when required and maintained in good health.Small ReleasesWorking Software is delivered to Customer at the end of every iteration – either for actual use or evaluation and to obtain feedback.Shared understandingCoding Standards are practiced so that there can be collective ownership and any team member will be able to understand the code.Pair Programming and Coding Standards ensure that code is not owned by one single person and is the responsibility of the team.Design is kept simple and continuously improved and revised to cater to the current functional demands. Design is not done up-front but done at regular intervals.XP teams use a common system of names to ensure a common understanding of the system.Programmer welfareSustainable PaceXP ensures the team members work at a pace that can be carried out for a very long time.  The system avoids situations where the team members are left wanting for work at times and then have to scramble to finish deadlines.Scrum and XP – What is common and different. Scrum and XP are two popular Agile Methodologies having the same larger goal of delivering to the customer incrementally and iteratively. Both the methodologies lay great importance to customer centricity, feedback mechanisms, continuous improvement and building sustainable empowered teams.  There are few differences in the implementing mechanisms of these methodologies.  Iteration Duration: Scrum Iterations last for 2 /3/ 4 weeks. XP iterations are usually very short – one week long or at the most 2 weeks. Role of the Customer: XP and Scrum have Release Planning and Iteration Planning sessions. But unlike Scrum, in XP the Customer drives the planning and schedules the Release.  The Customer continuously interacts directly with the Teams in XP, while in Scrum the Product Owner represents the Customer and Business. The XP teams ensure to deliver a working bug free system at the end of every iteration. Customer chooses to evaluate and provide feedback or Release to the end users. Scrum teams deliver working software at the end of every iteration. The Product Owner with the input from teams decides on the right time for General Availability (GA) Release depending on the Market Readiness, Customer input etc. Practices: Scrum recommends using Engineering Best Practices like TDD, Pair Programming, Code Refactoring etc. but XP takes it to another level by mandating these Engineering Practices. Scrum recommends that items planned within a Sprint are unchanged until the end, but in XP, teams accommodate a sudden change of priority even during the iteration, by swapping items if work has not started on it. Roles: Scrum has dedicated Scrum Ceremonies whereas XP does not prescribe it per se. Scrum has a dedicated Scrum Master who facilitates these events, but XP does not have a Scrum Master.  XP teams get guidance from Agile Coaches.  ScrumXP- Using the best of Scrum and XP Practices When there are two great practices, there is always a tendency to combine both and get the best of both the worlds. “Lean-Agile”, “Scrumban”, “ScrumXP” are some examples of hybrid terms that have become increasing popular by combining two philosophies (e.g Lean and Agile ) or two methodologies (e.g Scrum and Kanban / Scrum and XP). ScrumXP is a hybrid practice making the most of both Scrum and XP. XP has laid out some very effective Engineering practices that teams practicing Scrum can greatly benefit from.  Many teams practice Scrum as their process framework and include the very effective and efficient core Engineering XP Practices in their way of working. This gives rise to the highly productive ScrumXP hybrid model of working. Mostly the ScrumXP teams retain the Scrum Master and Product Owner roles within their teams to take care of the required orchestration and facilitation. ScrumXP and SAFe “Team and Technical Agility” is one of the key competencies of SAFe. By following  ScrumXP the SAFe teams take care of the team Agility through Scrum Practices and Technical Agility through XP Practices.  The robust Engineering practices of XP ensures the product being built is of very high quality, easily extendable, maintainable and sustainable. In conclusion, ScrumXP provides the best of both worlds. Teams can begin with Scrum and continuously improve by including the robust core XP Engineering practices like TDD, pair programming, code refactoring etc— not because it is mandated but because they find it effective. Although, interaction with the Customer is through a Product Owner, the Scrum teams can borrow the Customer Centric approach of XP to remain aligned with Customer expectations. 
What Is ScrumXP and How Does It Compare With Other Agile Frameworks
Blogs
5463
What Is ScrumXP and How Does It Compare With Other...

This article briefly talks about popular Agile m... Read More

The Spotify model - Agile

Many companies find it hard to scale Agile due to the various complexities that come with multiple teams, locations, time zones and different cultures. Over the past decade, many Scaling frameworks like SAFe, LESS, DAD have been introduced into the Agile world by various Agile practitioners and groups. This article is about one such scaling model called the “Spotify Model”. Origins of Spotify Model “Spotify” is a Sweden based music streaming company founded in 2006. The structure used by the company to scale agile across its various teams located in different locations came to be called as the Spotify Model. This model is becoming increasingly popular due to its flexibility and simplicity. Need for change in Organization Structure Today’s world is constantly changing due to social, political, and economic disruptions. The 2019-2020 COVID is a classic example of disruption in the entire world to the “business as usual”. To keep up with the disruption and competition, companies must be nimble and innovative to respond quickly and stay ahead of their peers. The hierarchical structures and organizational processes that worked well for decades are no longer enough to keep up with this fast-paced world. While traditional hierarchies and managerial processes are still very much required to run the show, the need of the hour is to also have an additional network structure operating in tandem with the traditional norms. The purpose of this network is to continually assess the business, the industry, and the organization, and react with greater agility, speed, and creativity than what has existed before.  There are so many examples around us where Start-up organizations thrive in the network structure and fail miserably when they have to scale, and cannot continue with traditional hierarchy and processes. In equal measure, around us are examples of Enterprise giants collapsing under the weight of the traditional hierarchy alone without the nimbleness and speed of the network structure.  Both the operating structures – the hierarchy and the network, are essential for today’s businesses to thrive. Kotter’s theory of establishing a dual operating system within an organization resonates heavily in the Spotify Model and compels us to draw parallels. In the Model we can see that there are innovative and thriving network structures and at the same time there is space to establish the traditional hierarchy as well. Spotify Model Squad: The Squad is the basic entity of the model which comprises the team that does the work. The Squad does not have a dedicated Squad lead but has a dedicated Product Owner.  The Product Owner tells the Squad “What” has to be done , prioritizes the work and maintains the backlog. Each Squad is self-organizing and can choose to follow Scrum, Kanban, XP or a hybrid of these. Squads are aligned to their mission, product strategy and short-term goals. Each Squad owns the release and delivery end to end. Typically, an infrastructure / DevOps Squad enables them to carry out smooth releases but does not do it for them. The Squad has access to an Agile Coach who runs retrospectives and Sprint Planning meetings. The coaches help the Squads to continuously improve. Tribe: A Tribe is a group of Squads that are related to each other by nature of the work being done by them. for e.g multiple Squads working together on the same product feature or closely related product features/ same product within a portfolio of different products.The number of people in a Tribe is recommended to be 100 in line with the Dunbar number. As per the Dunbar number, most people cannot maintain a social relationship with more than 150 people or so. All the Squads within a Tribe are co-located and physically able to interact in common areas dedicated for this purpose. There is a Tribe Lead who is responsible for creating a productive and an innovative environment for the Squads. The Tribe Lead can be part of a Squad as well.  Tribes meet often to showcase what they have been working on, what has been delivered and their learnings. The showcase could include the working software, new tools and techniques. Handling Dependencies One of the foremost challenges to resolve in a scaled agile environment are “conflicts and dependencies”. These can crop up during the development of a product among the Squads within a Tribe and also exist among Squads in other Tribes as well.   Dependencies could slow down or block the progress. Such dependencies are identified and are handled by reprioritization or through technical solutions. Sometimes innovative ideas could help remove the dependencies.  The end goal is to avoid dependencies between Tribes by making the Tribes self-organizing; and once that is achieved by having minimal dependencies among Squads within a Tribe. Survey for Continuous Improvement: A survey is done for all Squads at the end of every Quarter to understand the pain points and areas for improvement. For e.g multiple Squads having issues with the release process need urgent attention. One of the Squads not getting enough support from their Product Owner needs leadership intervention. Chapter: Certain disciplines/technological areas within the Tribe, like QA, Database Specialists, Front-end developers, Back-end developers, UX Specialists will benefit with regular discussions and interactions. People within these functions across multiple Squads and within the same Tribe constitute the Chapter. Constant communication within the Chapter members is encouraged. Each Chapter meets regularly to discuss their achievements and challenges in their respective areas of expertise e.g QA Chapter, UX Chapter, DB Chapter. There is a Chapter Lead who can guide the various members of the Chapter on “How” things can best be done. For e.g the QA Chapter lead can strategize the End-to-End Functional, Performance and Security Testing to be carried out for the new version of the product in an upcoming release. This will ensure the testers within all the Squads have a common well thrashed out testing strategy for the upcoming product release.  The Chapter lead can also be the line manager of the members in his Chapter, performing the traditional managerial responsibilities like people development, performance appraisals, career growth etc. The Chapter lead is also a member of one of the Squads in the Tribe, making him remain closer to ground realities.x` All the Chapter leads within a Tribe typically could report to the Tribe lead, and the Tribe Lead performs all the managerial responsibilities for the Chapter Leads within his Tribe as well as the next level Squad members of his Tribe.  Guild : A Guild is like a “community of interest” cutting across Tribes throughout the Organization/ Business Unit.  Imagine an Enterprise that has three Tribes each located in three different locations. There could be QA Chapters for each Tribe with respect to the location. There is also a need for QA members of one Tribe to exchange and share processes and learnings with QA members of the other two Tribes. The Guild is an organic structure that serves this purpose.  The Guild cuts across the Tribes spread across the organization across locations. Knowledge, tools, and practices are shared. For e.g the QA Guild includes all the QA Chapter members and in addition can include other members who are interested.  Guilds usually are not focussed on a specific release or delivery but on their area of expertise in a generic way. They have mailing lists, publish newsletters and conduct unconferences once in a while.  Spotify as a “Scaling Agile Model” Many of the foundational elements within the model become the backbone to scale agile in the organization adopting it. Spotify Model recognizes the need for a Network Structure within the organization to make it nimble and agile. The elements within the Spotify model help to establish Agile scaled to multiple teams spread across various locations and areas of work. The Spotify Model recognizes self-empowerment and self-organization, and at the same time aligns the Squads within a Tribe to work in tandem, in order to create complete and usable software products. The Chapters across Squads provide the environment for cross Squad collaboration. The Quarterly Survey in the Squads and handling dependencies within and across Tribes enables agility and continuous improvement. The Guilds help in improving the organizational culture to better adapt to the technological advancements and provide competitive readiness. Unique Benefits of the Model Spotify focusses on Agile Principles rather than mandating specific practices. Squads are autonomous to choose their own agile way of working. (Scrum/XP/Kanban/Scrumban etc. Not all Squads within a Tribe follow the same method) Specific Agile ceremonies and artifacts are not imposed on the Squad. Practices which work well with multiple Squads are automatically adopted by other Squads without the resistance that comes with standardization. This creates a balance of consistency across Squads along with the flexibility needed for autonomy. Though Squads are autonomous and loosely coupled they are tightly aligned by grouping them into Tribes. How Spotify is different from other Scaled Agile frameworks  While SAFe is a heavyweight scaled agile framework having many different flavours like Essential SAFe, Portfolio SAFe, etc, Spotify is more of a lightweight framework.  It might work very well for start-ups that are growing into medium Enterprises or for larger enterprises that are not ready yet for something as heavy as SAFe. The role of the Scrum Master is absent in Spotify, but the Squads have access to Servant Leaders in the form of Chapter and Tribe Leads and Agile Coaches. ConclusionThe Spotify Model has been a popular buzzword due to its unique nomenclature, flexibility and simplicity. It recommends the need for a community-based networking structure within the organization and focuses on the Agile Principles rather than Practices. It is a very unique and liberating Scaled Agile model and requires the practitioners to be extremely mindful and responsible while adopting it, so that it can be tailored for their specific organizational needs. 
The Spotify model - Agile
Blogs
5752
The Spotify model - Agile

Many companies find it hard to scale Agile due t... Read More

Why CSPO Certification Is Important For Your Career

This article looks at how and why the CSPO® Certification is increasingly becoming important for today’s Product Owner (PO). The article briefly discusses on the responsibilities of the PO, how the role is becoming mandatory within the organization in today's Agile landscape, what makes a great PO and about the CSPO Certification.Who is a Product OwnerThe Product Owner is a member of the Product Management / Business team who works closely with and is a part of the Agile team throughout the Sprints/Iterations. The responsibilities of a Product Owner(PO) spans across the aspects of People, Product and Process.PeopleThe PO is a conduit between Business and Engineering teams, acting as the “Voice of the Customer” and “Voice of the Business” to the teams,Is one of the members to create the Product vision and constantly communicates the same to the teams, and Is able to interact and communicate well with all stakeholders (Customer, Engineering , Sales, Marketing, Support etc.)ProductDefines and maintains the team’s Product backlog, Can answer “Why” a requirement has found a place in the product backlog, “Why” it is prioritized and “Why” the Customer wants the features, Can provide insights into what customer problem the requirements aim to resolve, Can provide Customer Journey Maps, User Personas and Real Life Examples, and Can determine the value that the product delivers to stakeholders and identify which product backlog items would deliver the most value.ProcessPrioritizes the product backlog and is able to provide the reasons and justification of prioritization to the teams, Is part of the regular Product Backlog refinements to refine User stories and Acceptance Criteria, Is available to the team throughout the iteration and provides continuous feedback, Seeks continuous feedback from Customers, and Is able to review the features and approve User Stories once they are completed.Significance of the PO roleTraditionally the Business/Product Management teams have suffered with constant shortage of time and conflicting priorities between dedicating time for Engineering teams and Customer facing responsibilities. Usually, the Customer facing responsibilities understandably end up as the higher priority,   leaving very little time for the teams.Earlier, the time dedicated by the Product Manager to Engineering teams was very little and elusive, sometimes limited to only email interactions. The Business teams were located at the customer sites and used to visit the Engineering teams occasionally, interacting with them through email or phone calls. As a result, the product and productivity suffered immensely.With the advent of Scaled Agile Frameworks and industry wide adoption of Agile, the role of the Product Owner has been laid out as a mandate and demands the increase of manpower in Business teams. Dedicated Product Owners are becoming increasingly indispensable and significant within teams. The role of the Product Owner role has come as a big relief for Engineering teams, because they are constantly in touch with the Business stakeholders as well as the team, and can smoothen and streamline communication channels.POs are often co-located with the Engineering teams, attending Daily (Stand up) Meetings, Refinement meetings, Sprint Review, Demos etc. in person with the team. They are also available anytime for quick feedback and queries doing away with time-zone difference and delays. The POs closely work with their Customer facing counterparts in the various customer locations, serving as the liaison between Business Teams and Engineering teams.The PO ‘s role is key for the success of the Agile way of working. It has become a “Must Have” role within the Agile landscape rather than a “Good to have” role. This has created a good demand for the PO role in the Software Industry. With the surging demand for POs in the industry, there are many professionals taking up the discipline of Product Management.  There are professionals from other functions like QA/Project Management/ Development etc. moving into the Product Management discipline as well.Who makes a “Great” PO?Although a PO satisfies all the roles and responsibilities required of his/her role, there are some traits and characteristics that set apart a great PO from the crowd.A great PO has conviction in the Product Vision and knows the priorities of the Business very well, and is able to articulate the same to the Engineering teams. Shows commitment in completing the team’s goals by providing early and timely feedback. A great PO is excellent in communication, able to understand the nuances of the various stakeholders and speaks in each one’s language (Customer, Engineering, Sales, Marketing, Support etc.) Does not take sides but does what is right for the given situation and for the Customers. Is able to say “No” and has the reasons for it.Is not a task master who dictates to the team but a great Influencer who has the answers to “what has to be done” and “why it has to be done”.   Trusts the team to know best on “How” things will be implemented. Negotiates well with the team for the Business but is fair in all interactions with the team winning the team’s trust. Is always curious in terms of the product implementation but does not interfere in the team’s approach of building the product.To really excel at the job, the PO has to constantly upskill and sharpen the tools he/she has to offer. The PO is required to have keen knowledge of the various practices and techniques that are being used by his/her peers in the industry, in order to stay ahead of the competition. The PO needs to be part of a “Community of Practice”, grow his/her network outside the organization and be clued into all the relevant trends in the industry.CSPO CertificationWith the growing demand for the PO role in the market, the Industry naturally creates ways to benchmark standards, uphold quality and nourish promising talent. The CSPO Certification is one such mark of standard and quality. It equips the Product Owner to become better at the job and helps certified individuals to stand out in the crowd. The CSPO course and the CSPO community offers the right environment for the Product Owner to excel in his/her job. The curriculum of the CSPO course is outlined below for your reference.ContentsScrum Basics Understand the Scrum Framework and workflow so that the PO   Agile Principles and Scrum Values Roles and Responsibilities Product Owner role in detail Scrum Master role at high level Team role at high level Product Vision Importance of Product Vision Creating the Product Vision Just enough preparations before creating the Product Vision Qualities of Product Vision Relationship between Product Vision and Product Road Map Estimation Estimation Levels and Techniques Accuracy is more desirable than Precision in Agile Estimation What can go wrong with Estimation   Difference between Estimating and Committing Product Backlog   Understand what Product Backlog is and is not Product Backlog Grooming Prioritization Importance and Benefits of Prioritizing Product Backlog Why everything cannot be Mandatory or Highest Priority Who should Prioritize Prioritization based on Multiple Factors Applying formal approaches to Prioritization   Giving leeway to teams to sequence work after prioritization Release Management Goal Iterative and collaborative Release Planning Quality and Technical Debt Releasing Software early and frequently Measuring velocity and Release Burndown chart Forecasting future releases Sprints Product Owner’s role in Scrum Meetings Collaboration between PO and Scrum Team, between PO and Scrum Master Team Commitment Understand why Sprints are Timeboxed and Protected from other distractions Concept of sustainable paceCareer Prospects and GrowthExisting POsFor people who are already wearing the Product Owner’s hat, the CSPO certification is like one more feather in their resume. Going through this course and certification will fine-tune their skills and help add multiple tools in their toolbox.Aspiring POsIn certain organizations, there might be team members exhibiting and playing the roles and responsibilities of a Product Owner without the role title. They would have acquired all the necessary skill-sets but not the formal official title yet. By attending the CSPO course and earning the CSPO certification they convey their readiness to play the role; and this gives the thrust necessary for their formal recognition into a Product owner’s role.Salary AspectsThe CSPO certification has global recognition and so will result in an increase in the pay package for a certified professional PO.What next for an accomplished CSPO?An accomplished CSPO can further his/her career prospects by taking up the Advanced CSPO course and certification. It will set the stage for the product owner to progress in their career path and play the role in a wider scope. Depending on the Organization type and structure it could be the role of a Product Manager, Product Portfolio Owner/Manager— and for the more adventurous, even the CEO of a startup! Some Product owners might choose to diversify into a Business Analyst role as well.In conclusion, the CSPO has become a benchmark certification for Product Owners in the Software Industry. It will definitely help existing and aspiring POs to sharpen and upgrade their skillsets. It is also a badge of accomplishment and achievement for a Product Owner, not only to set them as a class apart in their own organization, but also in their wider Product Management community.
Why CSPO Certification Is Important For Your Career
Blogs
4325
Why CSPO Certification Is Important For Your Caree...

This article looks at how and why the CSPO® Certi... Read More

Top Learning Outcomes of Leading SAFe 5 Certification

In any organization, the business decisions made by leaders play an integral role in determining its future. Their mindset, actions and strategies influence the functioning of the organization and workforce. True leaders continuously learn and upskill themselves to be on par with the changing times and stay ahead of the competition. This is where adoption of a Lean-Agile Mindset becomes crucial. It serves as an intellectual and leadership foundation for applying SAFe® principles and practices. A Lean Agile Mindset is undoubtedly the need of the hour for everyone and especially for professionals who oversee a company’s destiny.  This article briefly looks at SAFe® 5.0’s main offering – “Business Agility”, dwells on the foundational competency – “Lean Agile Leadership” and finally talks about how Scaled Agile Inc’s “Leading SAFe®“ course  is one of the front runners in providing knowledge and guidance for building SAFe’s foundational competency in an Enterprise.  What is SAFe®?  Enterprises span across multiple geographical locations, cultures and time zones. External stakeholders like Suppliers and Partners further add on to the organizational milieu. In spite of the scale, the enterprise has to be nimble and agile to keep up with ever changing customer needs and tough competition.Practicing Agile in an Enterprise has its very own challenges because of the scale at which it operates and the high stakes involved.SAFe® is an Agile Framework that recommends ways and methods for enterprises to implement, sustain and improve Lean and Agile Practices. SAFe®1.0 was introduced in 2011 and has evolved into the SAFe®5.0 version which was released in Jan 2020.What is new in SAFe®5SAFe®5.0 introduces quite a few things, of which we look at two important ones- Business Agility and the Dual Operating System.   John Kotter , thought leader of Change Management, famously describes the need for a Dual Operating System that combines the entrepreneurial capability of a network with the organisational efficiency of traditional hierarchy. SAFe® 5 recommends organizing a network around value streams, in addition to the traditional hierarchy, to create a dual operating system to achieve Business Agility.  Image source: Kotter’s Dual Operating SystemImage source: SAFe as a second organizational operating systemBringing agility within Engineering teams may not be enough to create products and solutions that are viable and saleable. Everyone who is involved in building solutions and products – Executives, Senior Leadership, Marketing, Sales, Finance, Engineering, Support, IT, Legal, Compliance, HR- has to be brought into the ambit of Lean and Agile Practices to achieve true Business Agility.The responsibility of making “Business Agility” a reality lies largely with the Leaders of the Organizations.Lean Agile Leadership CompetencySAFe® recommends seven core competencies to become a Lean Enterprise and achieve Business Agility.  “Lean Agile Leadership” is one of the foundational competencies of great significance.Without the buy-in, support and complete conviction from leaders in the organization, the SAFe® implementation cannot happen effectively.  Lean Agile Leaders play a key role in introducing, nurturing and sustaining the SAFe® transformation within the organization.What is required of a Lean Agile Leader?Growth Mindset: Leaders should have a realistic bent of mind to acknowledge a need for change within themselves as well as the organization. The leaders with the right outlook believe in the SAFe Core Values, the Lean-Agile Mindset, and SAFe Principles. Leading By Example: As the famous saying goes, “Actions speak louder than words”. So by walking the talk, leaders can influence scores of people to start adopting the Lean Agile practices, Values and Principles exhibited by themselves. Leading Change: Organizational transformation and change is a very difficult and rocky road to take. There are many thought leaders and researchers producing dedicated models, theories and books for bringing about change and sustaining it. A leader who sets himself on this path is aware of the challenges and is ready to lead the change successfully.   Image Source: Lean Agile Leadership CompetencyOne of the tools for leaders at the helm of bringing about change is having deep rooted knowledge, understanding and purpose about the practices they have to exhibit, and thereby influence the other employees in their organizations.Obtaining the Scaled Agile Framework’s “Leading SAFe®” Certification is the perfect way to start for Lean Agile Leaders. By getting themselves trained, leaders can begin the transformation journey armed with the necessary information.Leading SAFe® Course and CertificationLearning OutcomesThe 2 day long Leading SAFe® course results in the following learning outcomes:The knowledge and principles of Lean, Agile, DevOps, Lean Product Development Insights into achieving Business Agility through organizing around value Understanding of Lean Portfolio Management which emphasizes the need for Lean principles and Lean Budgeting The importance of PI Planning events, co-ordinating Multiple Agile Release Trains, establishing team and technical agility Customer-centric mindset and design thinking approach to Agile product delivery The importance of sustaining SAFe® transformation by creating Communities of Practice and fully empowered employees and teams. In short, the SAFe® Implementation Roadmap helps the leaders to chalk out their organization’s transformation journey. Who should take the Leading SAFe® Course? This course is just right for leaders who are in a position to influence employees, organizational structure and the future of products / solutions.  Executives of the organization that decide on the future course of business Business Unit Heads who are responsible for a Portfolio Heads of functions like Marketing/Sales/Product/IT/Engineering etc Agile Program Managers and Project Managers who steer programs and projects, Managers of teams Technology leaders like Enterprise and Solution Architects/ Distinguished Engineers/ Fellows who command a large sphere of influence on teams Leading SAFe® CertificationAttending the 2 day Leading SAFe® course is a requirement to write the exam, and participants will get access to all the study materials and the exam. Once the exam is   successfully completed, the candidate gets the below privileges as per Scaled Agile, Inc. Certified SAFe® Agilist PDF certificate Certified SAFe® Agilist digital badge to promote your accomplishment online One-year membership to the SAFe Community Platform, which includes access to the SA Community of Practice Access to Meetup groups and events that connect you with other SAFe certified professionals A variety of learning resources to support you during your SAFe journey Benefits of taking Leading SAFe®5 trainingEvery change starts with – what is in it for me? The Leading SAFe® course outlines a generic framework that is applicable to any enterprise. For an individual employee it is a learning for life and can be applied to any organization he/she is associated with.  The SAFe® Agilist Course and Certification is one of the prestigious achievements in the individual’s professional life earning him/her respect and recognition within the Agile Community.           A SAFe®5 certified professional is eligible for better prospects within their own organization or in other organizations, if and when there is a need for job change.  According to Forrester’s Q2 2015 Global Agile Software Application Development Online Survey-“The Scaled Agile Framework (SAFe®) is the most widely adopted enterprise Agile approach according to most survey data, with 33% using it”. With more than 70% of US Fortune 100 companies actively employing SAFe®, it is clear that the demand for Leading SAFe® is on a constant rise. Benefits of Leading SAFe®5 Training for the organization:Leadership is the foundation on which the “House of Lean” is built. A strong foundation of Lean Agile leaders, Managers and Executives help to create a learning culture for the organization by exhibiting the Lean Agile Mindset. This, in turn, paves the way for enterprise-wide transformation. Having a strong army of Agilists that are trained and certified helps the organization to sustain the principles of Lean and Agile.Agile ManifestoCorporate training for the leaders of the organization from a reputed Training provider like Knowledge Hut will ensure that all leaders are on the same page, hearing the same message at the same time. The training will become an opportunity for collaboration and the discussions during the training facilitated by the trainer can be tailored to suit organizational needs.   Why KnowledgeHut for Leading SAFe®5 Course?KnowledgeHut is a leading training provider offering a variety of accredited training programs for Corporates and Individuals. KnowledgeHut is a preferred training partner for various corporates.  KnowledgeHut offers training across 70 countries in over 250 industry-recognized courses. This includes a wide range of Courses in Agile and SAFe®.  Scaled Agile, Inc is the only certifying authority for SAFe® and KnowledgeHut is a Silver Partner of Scaled Agile, having trained more than 4000 professionals in various SAFe® certifications.  The Trainers for Leading SAFe® courses are an elite panel of accredited SPCs who also have years of experience as active SAFe® practitioners.  Learning happens through experiential workshops by accredited industry experts who bring in vast real-world experience imparting knowledge through in-class activities and simulations. Please refer here for all the details and the value-added services offered by KnowledgeHut for the Leading SAFe® 5 course. In conclusion, Scaled Agile Inc’s Leading SAFe®5 from KnowledgeHut will be a unique learning experience that will set the stage for success in one’s professional life. This credential benefits equally the individual, the organization and the larger cause of increasing the number of Agilists and improving the Agile Community at large.
Top Learning Outcomes of Leading SAFe 5 Certification
Blogs
6759
Top Learning Outcomes of Leading SAFe 5 Certificat...

In any organization, the business decisions made b... Read More