温馨提示：本站仅提供公开网络链接索引服务，不存储、不篡改任何第三方内容，所有内容版权归原作者所有
AI智能索引来源：http://www.a1qa.com/blog/scaled-agile-framework-levels-of-implementation
点击访问原文链接

Scaled agile framework: levels of implementation

进入原网站 导航首页
Scaled agile framework: levels of implementation Services Back Full-cycle testing services QA consulting Software lifecycle QA Ad-hoc testing Test automation Pre-certification testing User acceptance testing Crowdsourced testing Documentation services QA for digital transformation Engagement models Team augmentation Dedicated QA teams Managed testing services Fixed-price QA projects Quality engineering Shift-left testing Continuous testing Testing in Agile Multi-vendor environment Complete test coverage Functional testing Performance testing Cybersecurity testing Accessibility testing Compatibility testing Embedded testing Integration testing Localization testing Microservices testing Migration testing Regression testing Usability testing Systems & platforms Web apps Mobile apps Blockchain CRM ERP AR/VR Cloud Internet of things Medical devices Desktop Big data Salesforce SaaS AWS Azure Industries Back Software development Banking and financial services Telecommunications Media and entertainment Travel and hospitality eCommerce Insurance Healthcare Gaming Education Blog 25 April 2025 Building a safety net for banks: the role of testing in the ISO 20022 shift Approach Back How we work Testing environment Industry expertise Process maturity QA outsourcing ...With fast response to our requirements and professional approach, I can definitely recommend the cooperation with a1qa. Rainar Ütt, Head of Quality, InnoGames Portfolio Blog Company Back About us Clients QA Academy Awards News Values Events Contact us Case study a1qa helps roll out multi-regional mobile solutions for a leader in financial technology Contact us Blog Scaled agile framework: levels of implementation The 3-Level SAFe is implemented at the following levels: team, program and portfolio. Let’s focus on each of them focusing on what is relevant for the software tester involved. 27 March 2017 Agile Quality assurance Home Blog Scaled agile framework: levels of implementation Portfolio level Team level Program level Article by Vitaly Prus Head of testing department at a1qa We started talking about Scaled Agile Framework that helps to apply agile methodology across large development teams. SAFe is usually implemented on three levels. 4-Level SAFe is applied when there are hundreds of practitioners involved.

As for us, we’ve been working with 3-Level SAFe and will talk about it.

The 3-Level SAFe is implemented at the following levels: team, program and portfolio. Let’s focus on each of them focusing on what is relevant specifically for QA consulting practice and software testers involved.

Portfolio level We’ll start with the portfolio level, which is the highest level of concern in SAFe and is the scope of responsibility of the organization’s management staff.

A portfolio is a number of value streams. Value streams budgeting and implementation is discussed at the portfolio level. A Backlog with Business Epics is generated at this level. Software testing and developing teams have nothing to do here so we won’t dwell on it a lot.

Team level At the team level we deal with traditional agile teams and Scrum processes many of you are aware of. There is a backlog with user stories. When planning a sprint, teams define work and efforts necessary to meet their sprint obligations. Once the two-week sprint is over, the team meets for Sprint Review, or Demo, and demonstrates some scope of functioning software that can be released. Daily meeting also take place.

At the end of every iteration agile teams meet for Iteration Retrospective where they discuss what has been done well, what has not and what ways for improvement can be found. It’s worth mentioning, that developers and QA work side by side to deliver working software of the release quality. As you see, the process is the same as it’s in Scrum. The difference is that the sprint duration is restricted to 2 weeks.

Program level The program level is where most of the SAFe differences from Scrum lie. First of all, the size of the development team is larger. The whole team is made up of the usual sprint teams that are applied to the ongoing development mission. The whole team in SAFe is called Team of Teams and can be composed of 50-125 specialists.

The goal of the team is to deliver a Potentially Shippable Increment. “Potentially Shippable” is about the quality of the software, not its marketability. It should be free of defects and possess release quality. PSI is delivered during five sprints.

With every next PSI, end product gets more value. Value in SAFe is delivered by Agile Release Trains (ARTs), which is one of the center concepts in SAFe. The more products are delivered at the organization, the more ARTs there will be. In our project there was only one release train.

ARTs: why such a metaphor? Let us make it clear. Imagine that you are the customer and you have to get from Prague to Moscow by plane. To reach the final destination, you’ll have to tackle some risks and restrictions. You have to choose between the offered data options and align your timetable. You also have to purchase the flight ticket in advance and book a place on the plane.

A plane is said to be the most convenient means of transportation, but it isn’t free of risks either. The luggage can be lost, the flight can be delayed. Of course, it will take time to overcome any of them. In brief, you can’t be sure that you’ll reach the destination when you’ve planned to. This is exactly what stakeholders feel when the product is developed incrementally.

Now let’s imagine another situation. You travel by metro and have to get from one end station on line to the other. You go underground, buy a ticket and take a train. You don’t have to make any preparations beforehand and you are sure that you’ll get to the required station at the time needed because trains come and go regularly. Having missed one train, you’ll take another one in a couple of minutes.

The latest example describes the ARTs’ work perfectly well. They deliver value regularly (cycles of 5 sprints). As a result, it becomes easier to explain the stakeholders that features that haven’t been implemented in this sprint, will be implemented in the next one. The development process gets more predictability and the product development lifecycle shrinks. The customer should be calm and satisfied as s/he is aware that the release deadline won’t be missed and the end product will look like it was intended to.

So these are the basics of each level in SAFe viewed by the QA team. Next week we’ll answer the question: what are the key differences in product development in Scrum and in SAFe?

If you have any questions left, drop us a line in comments.

Share this: More Posts 13 February 2026, by a1qa 6 min read ROI and TCO in QA: How testing helps companies earn more and spend less Learn how to quantify the true business value of testing and align your quality strategy with the bottom-line goals that matter to the C-suite. Quality assurance Test automation 30 January 2026, by a1qa 5 min read Strategic QA: The foundation of digital transformation Digital transformation moves fast. Discover how modern QA helps you deliver change at speed by identifying high-stakes risks before they impact your reputation or your bottom line. Cybersecurity testing Functional testing Performance testing Quality assurance Usability testing 19 January 2026, by a1qa 4 min read Advancing QA and software testing processes with AI Uncovering the benefits companies gain when revolutionizing QA practices with the help of AI and tips to implement it. QA in eHealth Quality assurance Software lifecycle QA Test automation 15 December 2025, by a1qa 4 min read Compatibility testing: how to protect revenue, reputation, and delivery speed Modern users expect your app to work first time on whatever device they pick up. A clear compatibility strategy helps your team uncover environment-specific defects before launch, cut noisy support tickets, and keep revenue critical journeys running smoothly. Quality assurance 28 November 2025, by a1qa 6 min read Embarking on the journey ahead: QA trend playbook for 2026 Dive into the wave of QA advancements preparing to take center stage in 2026, arming yourself with the foresight you need to navigate any challenges with confidence.  Blockchain app testing QA trends Quality assurance Test automation 14 November 2025, by a1qa 5 min read QA’s role in a cloud move: before, during, and after Do not wait until go-live to find bugs. Learn how a continuous QA strategy turns a high-stakes cloud move into a controlled success. Cloud-based testing Functional testing Quality assurance 30 October 2025, by a1qa 5 min read Why media and entertainment needs smarter QA Your audience expects instant, crystal clear streaming every time. Learn how the right QA approach helps your team catch issues before release, protect ad revenue and keep viewers watching. Quality assurance 15 October 2025, by a1qa 3 min read 5 signs you need test automation When manual checks throttle delivery, speed and quality both suffer. If time to market is stretching and incidents keep coming, these five signals say automate now. Quality assurance Test automation 30 September 2025, by a1qa 4 min read eLearning with AI elements: a practical testing strategy leaders can trust AI lifts learning outcomes and engagement, but it also raises risk. Here is a clear, business-first testing strategy that helps leaders release reliable AI-powered eLearning, adapt it to local needs, and prove value quickly. Quality assurance Test automation Related posts Get in touch Name Please fill in the required field. Email Email address seems invalid. Company Phone Project description Please fill in the required field. I hereby give my consent for a1qa and its affiliates to process my personal data in accordance with Privacy Notice for the purpose of handling my request and responding to it. I am aware of the fact that I have the right to withdraw my consent at any time. Please accept the terms to proceed. Add an attachment This file is too large Up to 5 attachments. File must be less than 5 MB.
Allowed types: jpg, jpeg, png, svg, pptx, pdf, doc, docx, ppt, odt File input 1 File input 2 File input 3 File input 4 File input 5 Send a message Thank you! Thank you for reaching out! We’ll get back to you shortly. Close We use cookies on our website to improve its functionality and to enhance your user experience. We also use cookies for analytics. If you continue to browse this website, we will assume you agree that we can place cookies on your device. For more details, please read our Privacy and Cookies Policy. Accept United States
160 Clairemont Ave, Suite 200, Decatur, GA 30030
+1 720 207 5122

United Kingdom
3rd Floor, 5-8 Dysart Street, Moorgate House, London, EC2A 2BX
+44 204 525 7620

Subscribe to news Subscribe to news Full name Please fill in the required field. Company Please fill in the required field. Email Email address seems invalid. I would like to subscribe to a1qa’s newsletter and other marketing communication. By clicking this checkbox, I give my consent for a1qa and its affiliates to process my personal data in accordance with the Privacy Notice.

You can unsubscribe at any time by clicking the button "Unsubscribe" at the bottom of every email. Please accept the terms to proceed. Subscribe Thank you! Thank you for reaching out! We’ll get back to you shortly. Close Follow us © a1qa software testing company, 2026. All rights reserved. Privacy Policy Quality

智能索引记录