Real-Life Agile Project Management & Famous Success Stories

By Lulu Richter | August 26, 2024

Companies of all sizes have implemented Agile project management methodologies and found greater internal and external success. Here, we’ll look at famous real-life case studies in how large, medium-size, and small businesses implemented Agile.

Included in this article, you’ll find the following:

Famous Agile Project Management Success Stories

Agile project management can be transformative for legacy companies, as well as fast-growing startups. You can use Agile for projects of all sizes and scopes: Some famous examples of Agile companies include PayPal, Spotify, and Toyota.

As the Harvard Business Review wrote in 2018, some companies only use Agile, while some operate with a mix of Agile and traditional, more linear methodologies, such as Waterfall. Some companies are “born Agile” and innovate their methods as they grow.

Overview of Agile Methodologies and Outcomes: Famous Projects

Several large companies have used Agile to launch successful projects and refine processes. Below, you’ll find a chart of the most famous real-world examples of Agile projects, including those from PayPal, Spotify, Toyota, JP Morgan Chase, and more.

Company

Agile Methodology Used

Why They Chose It 

Outcome

BBVAScrum, KanbanTo drive greater adaptability in a fast-changing sectorImproved delivery times and product development, and increased transparency and organizational functionality
BoschScrumTo synchronize Agile and traditional teamsCreated more adaptable management operations,smoother company-wide collaboration, and continuous planning processes
CiscoSAFeTo improve efficiency, accelerate release cycles, and enhance employee satisfactionAccelerated workflows, reduced overtime, reduced defects by 40 percent, improved Defect Removal Efficiency (DRE) by 14 percent 
JPMorgan ChaseScrum, assorted Agile frameworksTo accelerate product developmentAccelerated innovation, shortened work cycles, quickened product delivery 
PayPalScrumTo ease bottlenecks, improve organization, and improve product release timesReduced bottlenecks, improved employee alignment, and increased product offerings (58 within first 6 months)
Philips ScrumTo improve quality, efficiency, and alignmentReduced release cycle from 18 to 6 months and shortened feature cycle by 58 percent
PlayStation NetworkScrum, SAFeTo accelerate product delivery and enhance employee cohesionImproved team alignment and morale, gained $30 million in savings within first year of implementation
SkyScrum, KanbanTo increase product delivery times and accelerate training and developmentAccelerated product and service development and delivery, improved efficiency and collaboration
SpotifyAdapted Scrum (“The Spotify Model”)To align teams across multiple cities and facilitate growthIncreased transparency, flexibility, and speed
ToyotaAdapted Scrum (“Scrum the Toyota Way”)To align product delivery with customer needs and build continuous improvementReduced waste and ensured ongoing efficiency 
The Vanguard GroupScrum, KanbanTo improve efficiency (Scrum); to synchronize teams and manage workflows (Kanban)Improved quality, increased productivity, accelerated innovation, enhanced flow, and limited work-in-progress (WIP) 


Remember, it’s not as simple as slapping on a new framework. In order to achieve newfound success with Agile, you’ll need to remain attentive and strategic, and follow principles of healthy Agile governance. Additionally, you should monitor your progress and perform regular Agile project retrospectives, so you can continually refine and adjust processes as necessary.

Below, we’ll take a closer look at these famous real-world case studies.

Smartsheet Agile Project Template

Plan, manage, and visualize your projects with Smartsheet.

Smartsheet simple agile project template

Stay on top of your Agile projects with this ready-to-use Smartsheet template. Track tasks by start and end dates, see how changes impact your timeline with dependencies, and keep everyone aligned with progress updates, task assignments, and automated workflows. Perfect for teams that need to adapt quickly and keep stakeholders in the loop.

Use the Smartsheet Agile Project Template

PayPal’s Scrum Approach

PayPal is remarkable for taking a “big bang” approach to Agile transformation. Rather than moving gradually from a traditional Waterfall methodology to an Agile methodology, the company transitioned all at once.

Before this transformation, the company had become disorganized, bottlenecked, and slow to release new products. Executives recognized that they needed a major change. Though the shift happened all at once, the company prepared extensively, assembling a team of more than 150 employees to plan for the transition. They engaged coaches and provided formal training in Agile methods to thousands of staff members.

In May 2013, the company adopted the Scrum model and established hundreds of cross-functional teams aligned around a two-week “sprint” (work) cycle. Within six months, the company had delivered 58 new products.  

The Spotify Model

Spotify’s Agile framework is so distinctive that it is known as “the Spotify model.” It was detailed by Henrik Kniberg and Anders Ivarsson in a 2012 white paper called “Scaling Agile @ Spotify.”

The company employs an adapted matrix structure of nesting groups. At the most local level, employees are divided into squads, cross-functional groups that are similar to Scrum teams, with distinct objectives. Squads can choose their own work methodologies and are meant to operate like mini-startups. Squads don’t have leaders, but they have product owners, who set priorities with broader objectives in mind.

Squads come together as tribes of 100 people or fewer, grouped according to business areas (e.g. music player, infrastructure). You can think of these tribes as incubators for the mini-startups.

Chapters are groupings within the tribe based around shared skills and competencies, while guilds are company-wide communities that meet regularly for knowledge sharing.

This unique Agile model is credited for helping to drive the company’s success. It has been studied at length and adapted by other businesses. 

Scrum the Toyota Way

Toyota is a pioneer in Agile methodologies. The popular Kanban method was initially developed in the 1940s by a Toyota engineer named Taiichi Ohno, who was inspired by American grocery stores that restocked their shelves according to demand, rather than pre-estimates of need. Ohno applied this principle to manufacturing, matching work to demand, rather than via top-down directives on what needed to be done and when.

Today, Toyota still provides an example of Agile project management, practicing an approach called Scrum the Toyota Way. This framework combines Scrum methodology with Lean principles, which the company helped pioneer through its Toyota Production System (TPS).

At Toyota, every team member receives formal training in Scrum, as well as coaching from Scrum Masters and coaches. Scrum methods enable rapid Plan Do Check Act (PDCA) cycles and embody the philosophy of continuous improvement, which Toyota calls kaizen. The aim is to align product delivery with evolving customer needs, while emphasizing core principles of waste reduction and continuous improvement.

Philips: Scrum at Scale

Philips, the health technology multinational, adopted Scrum as a core methodology in 2014. To implement Agile at scale, it enacted the Scaled Agile Framework (SAFe), a detailed approach for maintaining multiple Agile teams in line with broader objectives.

SAFe methodology includes the Agile Release Train (ART), an assembly of different Agile teams who work separately and coordinate among themselves. It provides guidelines for synchronizing these teams and how to introduce a management layer for overseeing multiple teams and projects, if needed.

Initially, Philips implemented SAFe in its software businesses with the goal of improving quality, efficiency, and alignment across teams. Through these efforts, Philips was able to reduce its release cycle from 18 to 6 months and shorten its feature cycle by 58 percent.

BBVA’s Agile Transformation

Banco Bilbao Vizcaya Argentaria (BBVA) started transitioning to Agile in 2014. The bank assembled small, self-managing teams to develop a new mobile banking application. The app was a success, which inspired BBVA to assemble more Scrum teams, or “digital factories,” for high-priority projects. Kanban methods helped with synchronizing and coordinating teams across different projects.

Transitioning to Agile sparked a broader transformation at BBVA. Agile methods led to internal changes, including a more fluid organizational structure. They also created the need for greater company-wide transparency — transforming the company at the enterprise level.

Agile for Acceleration at JPMorgan

JPMorgan uses an Agile philosophy to accelerate product development. Cross-departmental collaboration allows employees from different disciplines — for example, engineers and legal experts — to share insights and develop products more quickly and efficiently.

The company credits Agile methodology for help in getting products to market faster and accelerating innovation. Agile allows team members to break down large projects into smaller ones, shorten work cycles, and incorporate customer feedback. For example, an e-gifting initiative that JPMorgan launched in this manner took 6 months instead of the traditional 12.

Sony PlayStation Network: Aligning with Agile

In 2014, Sony Interactive Entertainment deployed the Scaled Agile Framework (SAFe) to speed its delivery of new PlayStation releases. The traditional Waterfall technique had proved too slow for the speed of demand. But Scrum on its own was also problematic and failed to create coherence over a network of more than 1,000 engineers.

The SAFe method brought teams into greater alignment. Teams worked in two-week sprints, while Agile Release Trains (ARTs) — essentially, teams of Scrum teams — met in person every 12 weeks to coordinate. The company’s director of engineering credited SAFe for savings of $30 million in its first year of implementation.

Cisco: Scaled Agile for Greater Efficiency

In 2015, Cisco implemented SAFe for its Subscription Billing Platform, as part of a broader shift to Agile methodologies. The previous Waterfall method had proved inefficient: One team began its stage of the development process only after the previous stage was complete, which created unnecessary delays. Release cycles ran over three months, teams frequently missed delivery deadlines, and employees worked long hours to make up the time.

Under SAFe, Cisco created three Agile Release Trains: Capabilities, Defects/Fixes, and Projects. Teams coordinated for 15 minutes each morning to share progress and determine priorities, which enabled greater cohesion. Workflows accelerated, overtime hours decreased, and employees felt better overall. The strategy also saw a 40 percent reduction in significant defects and a 14 percent improvement in Defect Removal Efficiency.

Learn more about how Agile project workflows work in our complete guide.

Vanguard: Scrum Meets Kanban

In 2007, Vanguard adopted Scrum methods to improve quality, increase productivity, and speed innovation in specific departments. Scrum created new challenges, however: For example, teams fell out of sync and failed to work evenly toward common objectives and regulatory requirements.

Kanban provided a solution to these problems. Visual project management boards allowed team members to conceptualize their work across the development cycle. This enhanced flow, facilitated feedback, and limited WIP. The Kanban Maturity Model, an Agile maturity framework for integrating and scaling the method, helped guide this evolution and further ease bottlenecks.

Agile Leadership at Bosch

Bosch is an Agile project management example that proves how important it is for leaders to understand Agile principles as they oversee Agile organizations. Bosch initially attempted a “dual organization,” where new business areas were Agile, but more traditional departments were not. This approach led to friction between departments and impeded operations. In 2015, the company adopted a more holistic approach to Agile. Significantly, leadership itself adopted Agile principles.

Management divided into cross-functional teams, tested different approaches, and interacted more directly with other division leaders. The company moved from an annual planning approach, with a fixed set of priorities, to more responsive, continuous planning. Today, Bosch still consists of both Agile and traditional teams, but Agile values are embraced company-wide. This has smoothed collaboration and allowed the company to adapt more quickly to changing markets.

Sky: Agile Beyond Software

Sky is a UK-based telecommunications company with a staff of more than 31,000. In 2011, Sky implemented Agile as part of its overall digital transformation. Previously, Sky had followed a Waterfall method that involved a six-week development cycle with two weeks of testing. Using Agile methods, Sky reorganized into cross-functional, self-managing teams and adopted a much faster pace of testing and release. This allowed Sky to debut new products and services rapidly and to meet market demands.

In 2016, the company began applying Agile in its HR department. Employees experimented and eventually adopted a specialized sprint method, along with a mix of Kanban and Scrum. This helped to break up silos and accelerate training and development.

Real-Life Agile Project Examples

Transitioning to Agile is a complex process that requires trial and error. But when implemented successfully, Agile helps teams manage workflows, speeds delivery, eliminates waste, and enables companies of all sizes to meet market demands.

Agile methodologies can be deployed at different scales, for teams working on-site and for those that work remotely.

In this section, we’ll look at real-life examples of successful Agile projects. We’ll divide these examples into large, medium-size, and small companies. There is no one-size-fits-all solution to implementing Agile; each category presents its own unique challenges and benefits.

To get started with Agile, consider using a pre-built Agile project management template or creating an Agile project charter to guide your efforts.

Real-Life Agile Project Examples from Large Companies

Large companies often face special challenges in implementing Agile, but the payoff can be huge. Look at large company case studies, such as FitBit and Lonely Planet, as a guide for how to transition to an Agile framework.

It can be difficult to coordinate across many autonomous teams and ensure alignment, and tensions can arise between departments when one works with Agile methodologies, while another remains traditional.

Methodologies such as SAFe and the Kanban Maturity Model can help businesses scale and implement Agile. Engaging third-party services, such as coaches and consultants can help ease the transition for employees and managers alike. Adopting a more central Agile mindset also helps companies evolve more broadly for changing markets and times.

Here are examples of Agile project management featuring large companies:

Company

Agile Methodology Used

Why They Chose It

Outcome

Chargebacks911KanbanTo increase interdepartmental collaboration Improved connectivity and collaboration between teams and eliminated redundancy 
FitBitScrum, SAFeTo meet rigid scheduling deadlines Improved scheduling and increased product innovation and delivery
Lonely PlanetKanban, ScrumTo increase job satisfaction and ease departmental bottlenecksIncreased productivity by 25 percent, improved job satisfaction and employee morale 
Roche KoreaScrumTo drive greater innovationGrew revenue by 30 percent, improved innovation, improved collaboration with hospital partners
Rush Order TeesScrumTo align product offerings with brand identity and integrate new technologies while maintaining production schedulesReduced in time to market for new products, increased customer satisfaction, improved collaboration and employee morale 
Ultimate SoftwareKanbanTo improve planning processes and cross-team collaborationImproved team clarity, flow, and productivity
VistaPrintScrum, KanbanTo shorten release cycles, ease bottlenecks, and increase collaboration between departmentsShortened release cycles from 18 months to three weeks, improved collaboration across departments, reduced lead times from eight weeks to nine days, reduced cycle times from two weeks to four days, increased employee satisfaction


VistaPrint Introduces Scrum and Kanban

With more than 6,000 employees, VistaPrint produces marketing materials for small businesses. It began as a printing company in the 1990s, but soon expanded to global e-commerce. VistaPrint exemplifies how viable Agile methodologies are, even beyond software.

In 2013, the company began transitioning its software team from Waterfall to Agile processes. This change shortened release cycles to three weeks from 18 months. However, the fast pace of software development created bottlenecks for the company’s creative teams.

As a result, the creative teams began implementing Agile, too. The company’s in-house advertising team received Agile training and adopted new methods and practices, such as a Kanban board to visualize workflow and break down tasks into smaller batches. Adopting an Agile mindset was crucial to this transition: Employees from different departments learned to think of each other as partners working toward common goals. These changes significantly reduced lead times (to nine days, down from eight weeks) and cycle times (to four days, down from more than two weeks), while increasing employee satisfaction.

Kanban at Ultimate Software

Ultimate Software, a human resources technology company, is an example of an Agile project that used multiple methodologies. The company started working with Scrum techniques in 2005. This offered advantages, but also posed challenges: Teams would plan their sprints, only to find that new regulatory changes (for instance, changes to tax law or insurance legislation) required them to start the planning process anew. Furthermore, Scrum recommends smaller teams than was optimal for the company. Cross-team communication proved awkward and costly. Ultimately, Scrum did not improve productivity.

In the end, integrating the Kanban methodology in 2014 proved more adaptable to company needs. Team members were able to visualize workflow on the Kanban board and limit WIP. Team size was determined according to what worked best. Kanban allowed the company to meet its Agile objectives of greater clarity, flow, and productivity.

FitBit Employs Scrum and SAFe

FitBit used Agile to solve a fundamental scheduling challenge. The company operates on a rigid production delivery schedule, determined by the holidays, when customers tend to buy its devices as gifts. Initially, FitBit used a Scrum approach to make these rigid deadlines. As the company grew, however, it needed to scale its Agile processes to meet greater demand.

In 2015, the company began implementing SAFe. Twelve Scrum teams met at the first of regular Program Increment (PI) events, an important ceremony where teams align under a shared mission and draft objectives for the next time frame. This approach helped teams hit their objectives ahead of schedule. The following year, FitBit debuted four new successful products and shipped more than 22 million devices.

Lonely Planet: Kanban and Scrum Example

Lonely Planet, a travel book publisher, provides a great Agile in non-software project example. Employees in the company’s legal department were overworked and dealing with a significant backlog. Their work processes were opaque to other departments, and as a result, colleagues often took them for granted. Employee satisfaction was low.

Taking inspiration from IT, the legal team adopted assorted Agile techniques, including Kanban and Scrum. The team used a visual board to track its workload, establish transparency with other departments, and review its process from start to finish. It limited WIP for each member and held daily standups and regular retrospectives.

The transition took fewer than 100 days and increased productivity by 25 percent. It also significantly boosted job satisfaction by clarifying tasks and lessening each member’s workload.

Roche Korea’s Agile Transformation

Roche Korea, a subsidiary of the Swiss healthcare multinational, started an Agile transformation in 2020. The overarching objective was to innovate new drugs for unmet needs and deliver value to the Korean healthcare ecosystem. Roche Korea created self-managing teams focused on treatments and patient groups, and it hired an Agile coach to support them. This allowed the company to better adapt to patient needs, while tackling new diagnosis and treatment areas, such as Alzheimer’s.

The following year, revenue grew by 30 percent compared to 2020. Agile methodologies have also allowed the company to collaborate more closely with Korean hospitals.

Chargebacks911 Uses Kanban

Monica Eaton is the founder and CEO of Chargebacks911, a risk mitigation firm for online merchants with 350 employees. “When I first launched my business, we relied on a Scrum system,” she says. “While there were advantages to this, it still had a number of limitations when it came to interdepartmental coordination. We struggled to bring different departments together and form a cohesive unit. We needed interconnectivity and close collaboration between teams, but didn’t know how to manage it, which resulted in a lot of wasted time and effort.”

The game changer came when Eaton read Eric Brechner’s book Agile Project Management with Kanban. Kanban helped the company streamline communication and collaboration across departments. “It’s a simple visual system, but that simplicity is an advantage. It allows for quick analysis of progress and accountability, which eliminates a lot of the redundancy you’d have in a non-Agile system. It also simplifies processes that might be a little opaque when using other Agile models like Scrum. Adopting Kanban revolutionized the way that we structured departments and managed projects. I really can’t praise it enough!”

Agile Example from Rush Order Tees

Michael Nemeroff is the CEO of Rush Order Tees, a custom printing and embroidery service with more than 250 employees. He credits Agile project management for allowing the company to respond nimbly to challenges as they arise.

“One major challenge was aligning the diverse range of product offerings with our brand identity,” he says. To address this, “We formed cross-functional teams, each focusing on different aspects of the products: design, quality, and market fit. This setup enabled us to adapt swiftly to feedback and make necessary adjustments without derailing the overall progress.

Michael Nemeroff

“Another challenge was managing the integration of new design technologies while maintaining production schedules. By using Agile methods, we could break down the project into manageable sprints. Each sprint had clear objectives, which allowed us to implement new technologies in stages and assess their impact incrementally. This way, we mitigated risks and ensured that each phase was successfully completed before moving on to the next.

“The outcomes were great. We saw a significant reduction in time to market for new products, an increase in customer satisfaction due to the higher quality, and more varied product offerings. The Agile method also fostered a more collaborative work environment, which boosted team morale and innovation,” reports Nemeroff.

Real-Life Agile Project Examples for Medium-Size Companies

Medium-sized companies also face unique challenges in transitioning to Agile. Sometimes a small company starts nimble, scales quickly, and finds that traditional methodologies don’t work anymore, but acquire bloat as they grow.

Below, you’ll find some examples of projects using Agile methodology at medium-sized companies.

Company

Agile Methodology Used

Why They Chose It

Outcome

LingScrumTo drive greater adaptability and continuous improvementAccelerated company growth, enhanced adaptability, improved customer satisfaction
MeVisScrumTo reduce technical debt and increase productivityReduced technical debt, increased productivity, improved employee morale
Penta TechnologiesScrumTo accelerate delivery times and break down silos Increased employee satisfaction (from 38 to 98 percent), improved collaboration across teams, reduced delivery times 
SipgateScrum, LeanTo increase cohesion and accelerate product development at a growing companyImproved cohesion and transparency, enhanced product development


Sipgate Creates Transparency with Scrum and Lean

Sipgate, a German telecommunications company, was founded in 2004. By 2009, the company was facing a crisis: Staff had grown to 70 (from just 13), but they suffered from a lack of cohesion and transparency, as well as interdepartmental conflict. New products were slow to develop, and management had become rigidly hierarchical and the organization too bureaucratic.

In 2010, the company decided to give Scrum a try. It hired a consulting firm and remade company culture around Agile and Lean principles, with empowered, cross-functional teams and biweekly Agile retrospectives for projects and sprints. The initiative was a success, and Sipgate cited the experience in its book of “work hacks” published in 2016.

Penta Technologies Example with Scrum

Penta Technologies is a software company that serves the construction industry. In 2018, the company faced slow delivery times and siloed teams. It brought in a new leadership team, which reduced executive overhead, and began implementing a Scrum framework in 2019. The transition involved company-wide training, self-selecting teams, and a focus on continuous improvement and transparency.

The results were awkward at first, but with time and commitment, the company saw gains. Three months after switching to Agile, 98 percent of staff reported feeling empowered at work, up from 38 percent.

MeVis Implements Agile

MeVis Medical Solutions, a medical imaging software company, started experimenting with Scrum methodology in 2009. The company was struggling with technical debt, which jeopardized customer satisfaction. At first, the results were positive, but after a while, gains slowed. In 2010, the company hired an Agile consulting service to provide structure for a broader transition, as well as training for engineers and product owners. In the end, MeVis was able to reduce technical debt and increase productivity by 10 to 15 percent, while improving employee morale.

Agile Case Study: Ling

Simon Bacher is the CEO and co-founder of Ling, a language learning app with 50–60 employees. Agile methodology helped “significantly” with the company’s growth, he says, allowing the company to respond quickly to customer needs. “We adopted an iterative and incremental development model, which allowed us to update the app based on users’ feedback. We used short sprints to handle critical aspects of the app, such as improving our voice recognition technology and expanding our content into more languages.”

Simon Bacher

When the company decided to launch live classes with language teachers, they were able to “pivot rapidly, create a new roadmap, and develop this feature in less than six weeks.” Agile is “not just a project management style,” Bacher says, “but a mindset that emphasizes adaptability, customer focus, and continuous improvement.”

Real-Life Examples of Agile Projects from Small Companies

Small companies can adapt especially well to Agile working methods, as they tend to have more flexibility than larger companies. Some companies are “born Agile,” while others employ Agile methodologies for particular projects.

However, small companies also face unique challenges, such as a lack of resources for third-party services and tools, personnel shortages, stakeholder resistance, and the difficulty of maintaining alignment while scaling.

Below, you’ll find examples of successful Agile projects from real-life business owners and managers.

Company

Agile Methodology Used

Why They Chose It

Outcome

altLINE SobancoScrumTo manage client needs more efficientlyImproved flexibility and adaptability, optimized cash conversion cycle
InspectNTrackScrumTo switch from a linear process to a more adaptable one, to client feedback and market requirements Accelerated development cycles and improved client satisfaction
Lake.comScrumTo implement new solutions safely and efficientlyImproved flexibility, enhanced services, increased customer satisfaction
TrainerFuScrumTo improve collaboration and adaptabilityIncreased collaboration and overall adaptability, improved product delivery times


Agile Framework at InspectNTrack

Sean Spittle is the lead software developer and Managing Partner at InspectNTrack, a safety inspection app. “When we first conceived InspectNTrack, we knew we had to develop a robust, user-friendly SaaS application that could handle the complexities of safety device inspection processes. Our initial project plan was traditional and linear, but we soon ran into issues. Development was slow, client feedback was harder to incorporate, and the market requirements seemed to shift faster than we could adapt. At that point, we decided to transition to an Agile framework. It was a game changer.”

Sean Spittle

"In the early stages of building our app, we started using Scrum, breaking down the development process into two-week sprints. Every sprint focused on delivering a small, functional piece of the app. The key was continuous client feedback. After our first few sprints, we had an initial prototype ready. We quickly called upon a handful of our clients to test this early version. The Agile approach allowed us to incorporate their feedback almost immediately into the next sprint. This cycle of ’develop, test, feedback, adjust’ was incredibly efficient.”

Initially, clients found their user interface confusing, but “because of Agile, we didn't have to wait until the end of a long development cycle to address it. We gathered their feedback, made necessary adjustments in the following sprints, and quickly improved the user experience. Seeing these changes unfold nearly in real time built a strong level of trust and satisfaction with our clients, contributing significantly to our early adoption rates.”

TrainerFu Adopts Agile Methodologies

Manobal Jain is the founder of TrainerFu, which provides apps for personal trainers to interface with clients. Before adopting Agile methods, “I was juggling multiple deadlines and felt like I was constantly putting out fires,” he says. “Tasks seemed to drag on, communication was fractured, and frustration ran high.

“My team adopted a system of short, focused sprints, tackling key goals in manageable chunks. Daily stand-up meetings kept everyone aligned and addressed roadblocks before they became major issues. This focus on communication and adaptability fostered a collaborative environment. As a result, the team delivered projects on time and within budget.” The team was happier and more engaged, and Jain felt “a newfound sense of control” over his work.

altLINE Sobanco Example with Agile

Gates Little is President and CEO of the Southern Bank Company. He gives an example from altLINE Sobanco, the bank’s commercial financing platform.

Little recalls using Agile methods to guide a client: “The project involved regular calculation and analysis of their cash conversion cycle. We had to identify key areas needing improvement. One major challenge was managing their accounts receivable efficiently. By breaking down the project into smaller, manageable sprints, we focused on streamlining their invoicing process first. This iterative approach ensured that we could quickly address issues and refine strategies in real time.

“Our client saw significant improvements in their cash flow within a few months. The Agile method allowed for flexibility and adaptability, which led to a well-optimized cash conversion cycle and better financial stability,” Little concludes.

Agile Case Study: Lake.com

David Ciccarelli is founder and CEO of Lake.com, a vacation rental company. While implementing keyless entry systems for its physical properties, Ciccarelli drew inspiration from Agile project management: “Just as in Agile methodology, we evaluated various keyless solutions in iterative cycles, and constantly refined our choices based on security needs and performance feedback. This approach ensured that each system was thoroughly tested and optimized before full implementation.”

At first, there was resistance from stakeholders “due to the perceived instability of continuous changes. However, through transparent communication and demonstrating incremental improvements, we were able to gain buy-in and support.”

The company also faced the challenge of coordinating across teams: “With Agile, ensuring that every team stays aligned can be tricky. We overcame this by holding regular cross-functional meetings and using collaborative tools to maintain clear and consistent communication.

“The outcomes have been overwhelmingly positive. The keyless entry systems we implemented not only improved security, but also enhanced guest satisfaction. The Agile approach allowed us to be flexible, quickly address any issues, and adapt to new requirements seamlessly.”

Use Smartsheet to Transform Your Company with Agile Methodology

From simple task management and project planning to complex resource and portfolio management, Smartsheet helps you improve collaboration and increase work velocity -- empowering you to get more done. 

The Smartsheet platform makes it easy to plan, capture, manage, and report on work from anywhere, helping your team be more effective and get more done. Report on key metrics and get real-time visibility into work as it happens with roll-up reports, dashboards, and automated workflows built to keep your team connected and informed.

When teams have clarity into the work getting done, there’s no telling how much more they can accomplish in the same amount of time. Try Smartsheet for free, today.

 

Discover a better way to streamline workflows and eliminate silos for good.

Try Smartsheet for Free Get a Free Smartsheet Demo