Knowledge Hub

In 2001, representatives from Scrum (Ken Schwaber and Jeff Sutherland), Extreme Programming (Kent Beck), Crystal (Alistair Cockburn and Jim Highsmith), Feature-Driven Development, and others created the Manifesto for Agile Software Development – aka the Agile Manifesto – which outlines 4 values and 12 principles. Self-named “The Agile Alliance”, this group of individuals who created the Agile Manifesto gave birth to what the world knows as Agile today.

Our Lean-Agile for Systems Engineering (LASE), is an approach to accelerate large complex system development while responding to changing customer needs. Let's understand the need for LASE

With the 7th RTE Summit around the corner, we checked in with our RTE of the Year 2021, Mayank Khare from KLM. We were curious to find out what his approach is at KLM and asked him to share his biggest learnings with us.

Organizations run business, while business delivers value to customers, clients, and users. Therefore, business is never forgotten. New valuable functionalities and features are always considered, as they are most likely to give us a return of our investment. When talking about hardware and software development, architecture and technical activities play an extremely important role. In many organizations, these are usually forgotten, or at least not treated as part of the business. Value may have a different meaning depending on your organization, team, and business. But the truth is, value is what your customer wants or needs. When you look at software development, for example, value means a new working functionality which is usable and proves a business hypothesis that we – as the customer, product manager, product owner, etc. – had in mind when gathering and prioritizing it in a backlog. Architecture, components, integration, deployment – all of those support the business that sits at the top, where it’s usually forgotten.

When was the last time you encountered something by accident, only to have it unexpectedly put you on the path to discovery? Unbeknownst to us (until recently!) Lisa Lykke Jordan had such an encounter when she first came across our RTE Summit in 2019. “I found out about the Gladwell Academy RTE Summit by accident, actually,” she said. While she was looking up information about SAFe, she encountered a website about the SAFe Summit, which in turn led her to stumbling across our RTE Summit website. As Lisa was a starting RTE at the time, she felt that the RTE Summit would hold more relevance for her than the SAFe Summit. “Because I was not that experienced as an RTE at the time (I had only been an RTE for about a year) and I was the only RTE in my company, I didn’t have anyone to actually spar with,” explained Lisa. As such, Lisa decided it would be good for her to expand her horizons and meet up with fellow RTEs from outside of Denmark who had more years of experience under their belts. Before she knew it, Lisa had her very first ticket to our RTE Summit -- the first of many, as she’d later learn! “All my hopes and expectations about the RTE Summit came true after the first time, so that was a good thing! That’s why I kept coming back,” noted Lisa.

If there is no trust and transparency within your Scrum Team, there is no team – just a group of individuals.

Collaboration is key to any organization’s success. In this article, we invite you to look at the benefits of collaboration in the workplace and the role that Scrum plays in this process. No matter how many members of the team work together, there is always some communication taking place between different departments and individuals within the organization. So, that brings us to the question: why does that level of communication need to be increased?

If you aspire towards a Scrum Master role, having some form of certification on your resume is a must. Scrum.org offers the acclaimed PSM learning track to support Scrum Masters in professionalizing their skills. Roland Flemm is a Scrum Trainer at Gladwell Academy and Scrum.org and has trained hundreds of Scrum Masters over the past few years. Newcomers begin their careers with a PSM I class to gain an understanding of Professional Scrum and the essence of the Scrum Master's role. Yet many Scrum Masters are hesitant to participate in a PSM II training course. This may be because it is unclear to them what the PSM II training has to offer. Perhaps this article will help offer a better understanding.

Agility, Kanban, Scrum -- what does it all mean? These terms can be incredibly disorienting when you find yourself diving into the world of working Agile for the first time in your life. But fortunately, learning about Agile doesn’t have to be difficult or stressful. In fact, when you break these terms down into their simplest form, they prove to be part of a straightforward methodology on the most productive manner of working in a collaborative environment: Agile.

In my previous two blogs, I explained the challenges that arise with scaling Agile, as well as solutions to these challenges. In this blog, I will discuss the best-known Agile scale-up model: the Scaled Agile Framework (SAFe). SAFe is probably the most widely encompassing framework of all the Agile frameworks. SAFe was published in 2011 by management consultant and software developer Dean Leffingwell, and it is promoted worldwide by publisher Scaled Agile, Inc.

In my previous two blogs, I explained the challenges that arise with scaling Agile, as well as solutions to these challenges. In this blog, I will discuss the best-known Agile scale-up model: the Scaled Agile Framework (SAFe). SAFe is probably the most widely encompassing framework of all the Agile frameworks. SAFe was published in 2011 by management consultant and software developer Dean Leffingwell, and it is promoted worldwide by publisher Scaled Agile, Inc.

Agility, Kanban, Scrum -- what does it all mean? These terms can be incredibly disorienting when you find yourself diving into the world of working Agile for the first time in your life. But fortunately, learning about Agile doesn’t have to be difficult or stressful. In fact, when you break these terms down into their simplest form, they prove to be part of a straightforward methodology on the most productive manner of working in a collaborative environment: Agile.