LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.
Select Accept to consent or Reject to decline non-essential cookies for this use. You can update your choices at any time in your settings.
Sign in to view more content
Create your free account or sign in to continue your search
Thanks for letting us know! You'll no longer see this contribution
When you are incorporating agile ways of working, the stakeholders are engaged and want to be. If they are not then the teams needs to bring this up in a Retro and reflect what practices for engagement are missing. Are the User Stories, Demos, and other places stakeholders should be engaged in not user focused? Are the teams priorities and work transparent and understandable to stakeholders?
When our work is understandable and meaningful to stakeholders they naturally want to be engaged!
Thanks for letting us know! You'll no longer see this contribution
I don't want to dodge the question, but
- shouldn't stakeholders be more engaged in an agile approach given its iterative and incremental nature?
- if stakeholders are not or difficult to engage/keep engaged, there's a fundamental problem with your, I mean their, initiative. If BAs need to "beg for attention", there's a problem.
I'm aware this may sound a bit naive, but a lack of stakeholder interest now is a bigger problem waiting to happen later. If you're in a mode of constantly selling the initiative, solve the fundamental issue of lacking stakeholder interest first, then implement later.
Thanks for letting us know! You'll no longer see this contribution
A key habit for getting and keeping stakeholders engaged is to respect their time. This can look like:
-Being really clear who needs to attend a meeting and why. (Breaking the practice of inviting anyone and everyone "just in case".)
-Facilitating working meetings where decisions get made, deliverables get updated, and meaningful outcomes are created that move the project forward.
-Being sure you go into a meeting prepared with questions and draft deliverables.
-Taking a moment at the end to celebrate the progress that's been made and confirm next steps.
The more stakeholders feel they are contributing, the more engaged they'll be.
Thanks for letting us know! You'll no longer see this contribution
This is a good one.
In my experience, the stakeholders have always been the ones who will not join meetings due to prior commitments or work or anything else. To keep them engaged, start by sending them the MOM of every meeting held without them and highlight the decisions or the plans that might be changed in their absence.
Keeping a reminder on a weekend to send them emails regarding what happened throughout the week is also helpful in some cases.
Thanks for letting us know! You'll no longer see this contribution
To keep stakeholders engaged in the agile business analysis process, maintain regular communication through brief, focused meetings like daily stand-ups or sprint reviews. Provide frequent updates on progress and highlight how their feedback influences decisions. Encourage active participation by seeking their input at key stages and showing them how the project aligns with their goals. Use visual tools like user stories, prototypes, or diagrams to make complex concepts more understandable. Address any concerns quickly and be transparent about challenges and solutions. By fostering collaboration and ensuring their voices are heard, you can keep stakeholders engaged throughout the agile process.