TArticles tagged with: Agile techniques

Applying an Agile Tool to Make Your Proposal Processes Better

Using lessons learned from each proposal effort to improve our approach the next time

We talk about it in our proposals. We know it works. Agile practitioners take it seriously and are diligent about its use. What is it? It’s the idea of using lessons learned from each proposal effort to improve our approach the next time. In the Agile Scrum world, they call it a Retrospective. APMP best practices suggest that conducting a lessons-learned review on each major bid opportunity is a critical best practice.  APMP suggests that after a proposal is submitted, the proposal team meets to discuss: What went right? What went wrong? What deficiencies can we correct in processes or approach, and what winning processes/methods should we repeat on future opportunities? Lessons learned should be well documented and stored for others to access and reference on future opportunities. I suggest that rather than wait until the proposal is submitted, we have our proposal teams capture lessons learned across the proposal lifecycle. … Continue reading Applying an Agile Tool to Make Your Proposal Processes Better

Continue reading...

Agile Proposal Management – Proposal Team Roles

Agile practitioners value individuals and interactions over processes and tools

The Agile Manifesto talks about people, communications, the product, and flexibility. With respect to people, Agile practitioners value individuals and interactions over processes and tools. It takes a team to produce a winning proposal, and they must work together effectively through productive interactions. This does not mean that processes and tools are not important, but simply that the interaction between people on the team is more important. Team efforts to explore the requirements, work through solutioning, ghost the competition, and clearly identify corporate strengths is better accomplished through personal communication, brainstorming, and collaboration than by email, spreadsheets, documents, or automated analysis tools. Consider today’s tools that can generate the compliance matrix for you. When I use one, I still prepare my own compliance matrix, and often have another person do the same to compare our interpretations, cross-check each other, and to ensure complete comprehension. As you adopt an agile, Scrum approach … Continue reading Agile Proposal Management – Proposal Team Roles

Continue reading...

An agile retrospective

Looking back at the past and into the future makes me think of the Proposal Postmortem. Performing a critical Lessons Learned review of what worked well and what can be improved is an important best practice in the lifecycle of a proposal. Do we always have at least one? How much attention do we give it before rushing off to the next proposal? Agile approaches like Scrum and Kanban employ a similar best practice called the Agile Retrospective. Its purpose is the same as a Proposal Postmortem—to capture Lessons Learned and improve processes and outcomes on future sprints (or proposal efforts). What can we learn from our counterparts in the software engineering field? What new perspectives can we adopt from the agile principles? After all, we are all developing a product—theirs is software, and ours is the proposal. Let’s explore this a bit… Retrospective (from Latin retrospectare, “look back”) refers … Continue reading An agile retrospective

Continue reading...