A new marketing vice president just joined a software startup and is concerned that the agile model does not provide the needed accountability for their role. What should the responsible project…

Establishing an executive review board for all features can introduce bureaucracy and slow down the agile development process, counteracting the benefits of agility.

While fostering open communication is generally good, it may not directly provide the tangible evidence of accountability and agreement fulfillment that a new VP might seek in an agile environment.

Agile review or demo sessions are specifically designed to showcase completed increments of work to stakeholders, allowing them to inspect the product, provide feedback, and acknowledge the team's progress. Leveraging these sessions offers a direct and transparent way for the marketing VP to see that the project is meeting its agreements and delivering value, thereby building comfort and trust in the agile process and addressing accountability concerns.

Requiring formal approval of all requirements contradicts the adaptive nature of agile, where requirements can evolve, and would revert to a more traditional, less flexible project approach.