To qualify for the PMI Agile Certified Practitioner (PMI-ACP®) credential, I documented my work on several agile projects. As I reflected on these experiences, I realized how well they illustrated many of the core principles embedded in the PMI-ACP framework.
Agile isn’t simply a methodology—it’s a mindset that values individuals and interactions, customer collaboration, responding to change, and delivering working solutions frequently. Below, I explore key agile principles through the lens of real-world projects I’ve led or contributed to. These weren’t large-scale enterprise transformations, but they did embody agile thinking, and helped me internalize the value of agility.
I’ll draw from three projects I worked on that addressed distinct business needs:
- Sales Data Mart – Consolidated spreadsheet data into a centralized reporting system.
- Interactive Sales Report – Developed a dynamic report to track key sales metrics.
- Customer Data Quality – Improved the accuracy and consistency of customer records.
1. Collaboration and Cross-Functional Teams
Agile thrives when teams are diverse in skill sets but united in purpose. Collaboration among cross-functional team members leads to faster decision-making and better outcomes.
Illustration:
In the data mart project, we built a small but effective team: myself (designer/developer), an accountant (subject matter expert), and the accounting manager (primary stakeholder). Instead of operating in silos, we worked closely each day—gathering requirements, assigning priorities, and demoing new versions of the data model. This structure eliminated rework and improved clarity.
2. Frequent Delivery of Value
Agile encourages teams to release usable outputs frequently, allowing stakeholders to gain value early and often—even before the product is “complete.”
Illustration:
In the interactive sales report project, we decomposed the work into small, functional pieces. Each metric, data filter, and aggregation level became a discrete deliverable. Even raw data tables were released early, and stakeholders found them immediately valuable. Every sprint ended with a demo of incremental progress—building momentum and trust.
3. Welcoming Changing Requirements
Instead of resisting change, agile teams embrace evolving requirements as opportunities to deliver a better solution.
Illustration:
The sales report project also highlighted this principle. Definitions of key metrics evolved from sprint to sprint, and stakeholders frequently updated their expectations. Because we worked iteratively, these changes weren’t setbacks—they were refinements. Our backlog adapted to reflect new understanding, and the final product was stronger for it.
4. Continuous Improvement and Adaptation
Agile promotes frequent reflection and course correction. Teams inspect outcomes and adjust behaviors, priorities, or processes to improve.
Illustration:
In the ongoing customer data quality project, continuous improvement is baked into the work. Initially, even the definition of “data quality” was unclear. Through exploratory sprints and stakeholder feedback, we refined our understanding and adapted our efforts. We’ve adopted elements of Six Sigma’s DMAIC (Define, Measure, Analyze, Improve, Control) cycle to measure quality improvement and guide iteration.
5. Stakeholder Engagement Throughout the Project
In agile environments, stakeholders aren’t passive recipients—they’re active participants. Frequent engagement ensures alignment and shared ownership of the outcome.
Illustration:
Across all three projects, but especially in the data mart and customer data quality efforts, we involved stakeholders continuously. In the data mart project, the accounting manager was present during daily standups, contributing directly to decision-making. In the customer data quality work, stakeholders helped us validate assumptions, prioritize datasets, and redefine quality metrics—each sprint a learning opportunity for all involved.
6. Simplicity and Just-in-Time Planning
Agile favors simplicity—the art of maximizing the amount of work not done—and planning work only to the extent necessary for the next sprint.
Illustration:
In the data quality project, we didn’t attempt to define all cleansing rules upfront. Instead, we made educated guesses, cleaned small data samples, and then measured the impact. This minimalist, hypothesis-driven approach prevented over-engineering and allowed our understanding of quality to evolve organically.
Building Agility One Step at a Time
While preparing for the PMI-ACP exam, I realized that passing the test wasn’t just about memorizing frameworks or terminology—it was about reflecting on how I’ve applied agile principles in practice. Each of these projects gave me a deeper appreciation for agile as a mindset rooted in value delivery, adaptability, and collaboration.
The work wasn’t perfect or glamorous, but it was real—and that’s where the learning happens. These experiences helped shape not only my PMI-ACP application but also the way I approach projects going forward.
