We asked industry experts to share how becoming more Agile has changed their approach to planning and executing projects. Here are the key lessons they’ve learned in the process. Learn how Agile methodologies will help you embrace change, empower your team, and make rapid, yet thoughtful decisions.
- Agile: Our Startup’s Compass
- Adapting Quickly in Roofing Business
- Empowering Teams for Innovation
- Ditching Perfection for Progress
- Responsive Execution at Pumex
- Structuring Interaction with Stakeholders
- Rethinking Problem-Solving in Data Recovery
- Planning and Executing with Flexibility
- Iterative, Responsive, Value-Driven Process
- Prioritizing Flexibility and Incremental Development
- Flexibility and Rapid Decision-Making
- Dynamic, Feedback-Driven Strategies
12 Expert Lessons of Agile PM
Agile: Our Startup’s Compass
As CTO, navigating today’s tech landscape means embracing agility. Business and technology shift rapidly, especially in healthcare, e-commerce, and custom enterprise solutions. Agile isn’t just a buzzword; it’s our survival strategy.
Before, planning felt like carving stone–inflexible and resistant to change. Now, it’s more like sculpting clay, constantly refined with feedback.
- Iterative Progress: We break projects into sprints, delivering incremental value. This allows us to adapt to evolving requirements and market shifts.
- Continuous Feedback: Regular reviews with stakeholders ensure we’re always aligned. We prioritize open communication and transparency.
- Flexibility Over Rigidity: Rigid plans often fail in dynamic environments. Agile allows us to pivot quickly, adjusting priorities as needed.
- Empowered Teams: Agile empowers our teams to make decisions and take ownership, fostering a culture of innovation.
The biggest lesson? Great communication is the cornerstone of successful agile projects.
- Open Dialogue: Foster an environment where everyone feels comfortable sharing ideas and concerns.
- Regular Sync-Ups: Daily stand-ups, sprint reviews, and retrospectives keep everyone informed and aligned.
- Clear Expectations: Define clear goals and deliverables for each sprint.
- Active Listening: Truly listen to feedback from stakeholders and team members.
Agile isn’t just about speed; it’s about building quality solutions that meet real-world needs. By embracing iteration, feedback, and consistent communication, we deliver value to our clients while staying ahead of the curve.
Ritesh Joshi
CTO, Let Set Go
Adapting Quickly in Roofing Business
Becoming more agile has completely transformed how I plan and execute projects, allowing me to adapt quickly to industry changes and unforeseen challenges. In the roofing business, where weather conditions, supply chain disruptions, and insurance complexities can shift overnight, agility has been the key to staying ahead.
Earlier in my career, I focused on rigid planning, expecting everything to go as outlined. However, I quickly realized that flexibility and rapid decision-making were just as important as having a solid strategy. Agility means embracing real-time problem-solving, streamlining processes, and empowering my team to make swift, informed decisions. One key lesson I’ve learned is that agility isn’t about abandoning structure—it’s about refining it to allow for quick pivots without losing focus.
For example, during the pandemic, supply shortages threatened project timelines. Instead of delaying jobs, we adjusted our sourcing strategy, expanded supplier partnerships, and kept communication transparent with clients. This adaptability not only maintained our operations but also strengthened trust with our customers.
Agility has made my leadership more proactive and solutions-driven, ensuring that no matter what comes our way, we’re always prepared to navigate challenges and deliver top-tier service.
Trenton Wisecup
Founder and Owner, Arrow Roofing Services, LLC.
Empowering Teams for Innovation
One of the biggest lessons I’ve learned about leadership in an agile organization is the importance of adaptability and trust. In an agile environment, priorities can shift quickly, and as a leader, I’ve found that empowering teams to make decisions fosters innovation and efficiency. Early in my career, I focused heavily on detailed planning and oversight, but I quickly realized that agile teams thrive when given autonomy and clear goals rather than micromanagement. This shift allowed my teams to move faster and remain flexible without losing focus.
My leadership style has evolved to prioritize communication and collaboration. I regularly hold brief check-ins to keep projects aligned while giving team members the space to own their work. For example, when launching a time-sensitive SEO campaign, my team identified key changes in search algorithms mid-project. Instead of sticking to the original plan, we adjusted strategies based on real-time data, leading to higher rankings and increased traffic. This experience reinforced my belief that agile leadership is about guiding teams with trust, empowering quick decisions, and creating an environment where adaptability is embraced.
Brandon Leibowitz
Owner, SEO Optimizers
Ditching Perfection for Progress
Becoming more agile has meant ditching perfection in favor of progress. Instead of over-planning every detail, we move fast, iterate, and adjust on the fly. One key lesson? Waiting for “perfect” kills momentum. We’ve learned that launching something good today beats launching something perfect six months too late. Agile keeps us adaptable—if something isn’t working, we tweak it instead of doubling down on a flawed plan. The biggest shift? Seeing plans as starting points, not rigid blueprints. Flexibility isn’t a weakness—it’s how you stay ahead.
Justin Belmont
Founder & CEO, Prose
Responsive Execution at Pumex
Becoming more agile completely transformed how we plan and execute projects at Pumex. In the past, like many companies, we relied on rigid, long-term roadmaps that assumed all variables could be anticipated upfront. But real-world projects, especially in software development, don’t work that way. Agility forced us to shift from “predict and control” to “adapt and iterate.” Now, instead of locking in exhaustive project scopes, we focus on delivering value in smaller, iterative cycles, continuously refining based on real-time feedback. This approach doesn’t just improve efficiency, it reduces risk and ensures we’re always aligned with the client’s evolving needs.
One of the biggest lessons we learned was that agility doesn’t mean abandoning structure, it means adopting the right kind of structure. Early on, we faced the challenge of balancing speed with strategic direction. Moving too fast without clear priorities can lead to wasted effort. To counter this, we implemented regular sprint retrospectives and cross-functional collaboration to ensure agility doesn’t become chaos. By embedding agility into our culture, rather than treating it as just a methodology, we’ve been able to scale projects efficiently, pivot when necessary, and consistently deliver high-value solutions.
Antony Marceles
Founder, Pumex Computing
Structuring Interaction with Stakeholders
We have adopted several changes to become more agile in our projects. The main difference has been how we structure the interaction between the project team and the external stakeholders (i.e., product owner, executive sponsor, end users). Instead of having a single planning meeting at the start of each product where we define the requirements and objectives, we have now broken down the projects into two-week length milestones called “sprints.”
At the start of each sprint we have a sprint backlog planning session where we review the scope, objectives and requirements for the overall project and the upcoming sprint. We may change the scope/priority of the work based on external factors including market conditions, customer feedback, and changing business priorities. At the end of each sprint, we have a sprint review where we review the deliverables of that sprint, provide feedback and use that as input into the next sprint. If we find there are issues with what was executed, we can use the next sprint to course correct.
One of the key lessons has been the need to change the sequencing of how we are doing quality assurance and verification activities. Previously they would have been performed toward the end of the project, once the design and development activities were completed. However, with two-week sprints and the ability to adjust scope at the start of each new sprint, this doesn’t make sense. Instead, we have the quality assurance team involved up front during the initial planning phases, developing the QA plans in concert with the overall sprint plan. The QA team will review the requirements and objectives at the start of the sprint to assess their quality (in terms of how well defined, and how testable they are) and determine the level of risk associated with the delivery of the work.
Adam Sandman
Founder and CEO, Inflectra
Rethinking Problem-Solving in Data Recovery
Being agile made me rethink how I solve problems. Unexpected problems happen a lot in data recovery, and strict plans don’t always work. A big client once had a very important database that was badly corrupted, and our standard fixes didn’t work. We didn’t stick to a set plan; instead, we built the answer as we went along, making changes based on the results of live tests. The fix recovered 95% of the data they lost and is now permanently built into our software. The most important thing to learn is to be fluid, act quickly, and change based on facts, not guesses.
Alan Chen
President & CEO, DataNumen, Inc.
Planning and Executing with Flexibility
Making more agile changes is completely about how we plan and execute projects. Earlier, we believed in detail, thinking that we had all the answers. But reality? Things rarely occur according to plan. Now, we focus on setting a clear direction, but as soon as we go, we leave room to adjust.
One of the biggest lessons we have learned? Agility is not only about moving fast—it is about doing smart work. Instead of aiming for a large-scale project scope, we break things into small, attainable milestones. It helps us to stay on track and adapt quickly if something is not working. A simple but effective change we made was to include the first customers in this process. Instead of assuming that we know what they want, we share the prototype quickly, receive their feedback, and make adjustments before going too far in the wrong direction.
Another big shift has been how we handle team feedback. Retrospectives used to feel like a box we had to check. Now, they’re useful. If something isn’t working, we tweak our approach immediately rather than wait until the project is over.
At the end of the day, agility isn’t about having fewer plans; it’s about having better ones. And the best plans are the ones that can change when needed.
Vikrant Bhalodia
Head of Marketing & People Ops, WeblineIndia
Iterative, Responsive, Value-Driven Process
Becoming more agile has fundamentally shifted how we plan and execute projects, making the process more iterative, responsive, and value-driven. Instead of rigid, long-term plans, we now focus on shorter sprints, continuous feedback, and delivering incremental improvements. This approach allows for faster course corrections, better alignment with client needs, and reduced risk of wasted effort.
One key lesson learned is that agility isn’t just about speed—it’s about adaptability and collaboration. Early on, we assumed that moving fast meant delivering more, but we quickly realized that agility is about delivering the right things at the right time. By fostering cross-functional collaboration, empowering teams to make decisions, and keeping a clear feedback loop with stakeholders, we’ve been able to improve efficiency while maintaining quality.
Sergiy Fitsak
Managing Director, Fintech Expert, Softjourn
Prioritizing Flexibility and Incremental Development
A more agile mindset has influenced how I plan and execute projects by prioritizing flexibility, incremental development, and ongoing communication. As a result, instead of strict, long-term plans, I focus on having a clear outline of short-term milestones, continuously refocusing priorities, and making data-driven decisions in between. Such collaboration has not only increased efficiency and responsiveness but also overall project outcomes.
One important lesson I’ve learned is that flexibility is not the absence of structure. You need a rigorous framework for flexibility, so that you can pivot quickly while maintaining alignment with your broader objectives. A combination of structure and adjustment gives teams the safe space to do their best work, and yet allows them to respond to every new challenge and opportunity in an agile way.
Spencergarret Fernandez
SEO and Smo Specialist, Web Development, Founder & CEO, SEO Echelon
Flexibility and Rapid Decision-Making
One of the biggest lessons I’ve learned about leadership in an agile organization is the importance of flexibility and rapid decision-making. In an agile environment, things move quickly, and change is constant, so being a leader means embracing uncertainty and encouraging the team to adapt swiftly to shifting priorities. I’ve learned that my role is less about providing all the answers and more about creating an environment where innovation thrives and empowering the team to take ownership of their work.
As my leadership style has evolved, I’ve become more focused on open communication. In agile teams, clear communication is key, and leaders need to support this by being accessible, listening to feedback, and making adjustments where needed. I’ve learned to be more hands-off, allowing the team to experiment and fail quickly, often leading to more creative solutions and growth. The ultimate goal is to guide the team toward the vision while giving them the autonomy to make decisions and drive the work forward. In this environment, leadership is less about authority and more about being a supportive coach who provides clarity, removes obstacles, and drives continuous improvement.
Kristin Marquet
Founder & Creative Director, Marquet Media
Dynamic, Feedback-Driven Strategies
Agility has fundamentally reshaped how projects are planned and executed, moving from static roadmaps to dynamic, feedback-driven strategies. The biggest lesson? Plans are just starting points—real success comes from constant adaptation. The market, customer needs, and technology evolve rapidly, and the ability to reassess priorities, make informed decisions on the fly, and execute with speed is a competitive advantage. Agility isn’t just about efficiency; it fosters innovation, resilience, and a culture that thrives on change rather than fearing it. The shift isn’t just operational—it’s a mindset that transforms how success is defined and achieved.
Anupa Rongala
CEO, Invensis Technologies
Image Credits: Photo by Daria Nepriakhina 🇺🇦 on Unsplash
