Enable javascript in your browser for better experience. Need to know to enable it? Go here.
Blogs Banner

Every agile BA's go-to list of 101 project-tracking questions

The agile framework is a brilliant way to build and deliver scalable software solutions irrespective of size or complexity. The foundational principle of agile teams is continuous collaboration and conversation, which helps discover and maintain a consistently holistic and interdependent business view. This approach also keeps the team and client engaged ensuring resounding success until the end of the project, and then some.

Given that intent, it lies with Business Analysts (BAs) to keep track of all the possible questions that come up during the life cycle of an agile project. From my work on the field, I have put together a guide, a list of questions that every BA needs to ask to keep their projects on track.

         Familiarizing oneself with the client’s ecosystem

  1. Who is my client?
  2. What is my client’s business and market of operation?
  3. What is my client’s business model?
  4. Who is my client's target audience?
  5. Who are the internal and external decision makers/ influencers relevant to my client’s business?
  6. Who are my client’s competitors?
  7. What differentiates my client from his/her competition?
  8. Who is the executive/project sponsor (deciding on budgets and roadmap) on my client team?

    Drawing out the scope of work (for the service provider)

  9. What can I learn/use from the target audience?
  10. What is the product/service that my client needs help with?
  11. What is the product/service’s Unique Selling Property (USP)?
  12. What is the landscape of the product/service?
  13. Will the intended solution solve the problem at hand or, does the right gap need to be identified?
  14. Why this solution and not something else?
  15. Is the problem an internal service or process related issue for my client? If yes -
    • What is my client’s problem?
    • Why is that a problem?
    • At present, where does it hurt my client the most?
    • What factors surrounding the problem are affected?
    • Who are the people/users facing the problem?
  16. What ideas/solutions should we look at?
  17. What are the pros and cons of those ideas/solutions?
  18. Which solutions would I recommend?
  19. Why would I recommend that solution/s?
  20. Is this a green field or brown field product/service
  21. If it is a green field product/service-
    • Which market is my client targeting?
    • What is unique about that market?
    • Who are the potential users in the market?
    • What would make this product/service special/irresistible?
    • How is my client planning to market this product/service?

    Story wall

    Plotting the product/service’s functional feature and prioritizing:

  22. What will be the most regularly used product/service features?
  23. Which of those features should be developed first?
  24. Is everyone from my client’s team invested in the current priorities?
  25. How would we define my client’s success?
  26. Are the prioritized features going to help with that success?
  27. By when should this success ideally happen?
  28. How do I rank what (or combination of what) is important to my client - saving time, saving money, fine-tuning the product/service?
  29. Do I have all the information I need, to split chosen features into agile stories?

    Identifying focus areas to ensure optimum project/partnership outcomes:

  30. What kind of research/homework should I carry out on the product/service?
  31. Why is my team uniquely positioned to help my client?
  32. Who are the stakeholders (to be mapped) from my client’s team?
  33. Who from my client’s team will the team and I be collaborating with (plotting individuals’ level of engagement vs. their influence on my client’s team)?
  34. Have I/my team interacted with all these individuals?

    Ensuring successful delivery right from the beginning:

  35. Are my stories the right (estimable) size?
  36. Is the User Experience/User Interface (UX/UI) design available for the solution.
  37. Is the UX client-approved?
  38. With stories, estimates, and UX in place, can a release be planned?
  39. Is the release plan, budget, and timelines client-approved?
  40. Have I started building my RAID log? If yes -
    • What are the risks involved in the solution?
    • What assumptions are being made at the project-start?
    • What issues have bubbled up already?
    • What are the dependencies to be considered: people availability, required resources, and software integrations.
    • What are the important non-functional requirements that are needed to build the solution?
  41. What does my ‘continuous communication plan’ of progress and pitfalls (project progress) look like?
  42. How can I engage the executive or project sponsor in communication?
  43. Have the functional dependencies been addressed?

    project partnership

    Getting into the groove of implementation:

  44. How is the project being set up, once development starts?
  45. Are all the team members on board from Day 1?
  46. If yes - are roles, responsibilities, and requirements of every team member clear to all?
  47. If no, how can new members be brought up to speed?
  48. Is the functional context and landscape of what is being developed clear to the team?
  49. Am I ensuring efficient project tracking using a project management tool like Jira, Mingle, Trello, etc.?
  50. Am I ensuring that the team has understood a story’s requirements and boundaries before development kicks off?
  51. Am I ensuring that the project wall is up to date and the client’s side product owner/manager has reviewed the stories, before development?
  52. Am I ensuring that completion means all the acceptance criteria covered in a story are developed (dev box testing/volley ball)?
  53. Am I focussing on Iteration N+1 stories while the team is focusing on Iteration N?
  54. Are all stories slotted for Iteration N progression, and doable throughout the iteration?
  55. Do any stories have blockers?
  56. If yes, can the blocker be removed quickly?
    • If yes, can the story still be completed within the iteration?
  57. If neither is possible, can another story be brought in to ensure the pace of development is unaffected?
  58. Are there plans for automating some of the testing?

    Managing delivery and the client relationship:

  59. Are all developed stories ready for client showcasing?
  60. At the showcase, are progress and pitfalls highlighted for communication?
  61. Have I planned for a Retrospective?
  62. Are delivery heads and client partners updated on progress and pitfalls?
  63. Has the team reviewed the N+1 iteration stories before the iteration begins?
  64. Does every team member agree on the way forward?
  65. Are we looking at a cost burn up?
    • If yes, are we burning more or less than planned?
    • If more, how do we highlight this?
    • If less, why? And how does this impact scope management?
  66. How is the scope burn up? Are we tracking more or less than planned?
  67. Is the scope tracking lesser than planned?
    • If yes, why?
    • Will we be able to catch up with the plan.
    • If we cannot catch up, then what factors should feature in my client conversation to decide - scope cutting, workarounds, timeline changes, etc.
  68. Is the scope tracking more than planned?
    • If yes, is it due to constant spillovers?
    • If not, is this the new normal?
  69. Are we tracking defects?
  70. Are they tracked per environment (development, user acceptance, production, etc.) or development cycle (iteration, sprint etc).
    • How are these defects prioritized and included in the plan?
    • What inputs from the BA/Project Owner can help with defect specifications and triaging?

    Collaborating and communicating for wholesome success (team happiness, delivery on time, knowledge quotient, client satisfaction, trust quotient, etc.):

  71. What inputs should the BA share during Dev huddles?
  72. Is there continuous check and showcase of completed work with the client (iteration planning and feature demo).
  73. Are key participants part of planning meetings.
  74. Are priorities addressed/changed when these meetings take place?
  75. Are my clients actively looking through completed functionalities?
  76. If not, why? What can be done to ensure they look at completed work?

    managing delivery

    Consistently tracking progress and removing blockers:

  77. Do my clients have access to a production like (UAT) environment to test the functionality?
  78. Are we continuously integrating newly developed features into the UAT environment for clients’ review?
  79. When my clients are testing the solution, are we receiving feedback on the functionality?
  80. Is the feedback about newly defined functionalities or misses from our end?
  81. How is my team tracking the feedback?
  82. Are new stories being prioritized in the backlog?
  83. Are there priority-re-setting workarounds for the feedback.
  84. How am I tracking my RAID log?
  85. How am I mitigating the RAID items?

    Last few miles of delivery:

  86. Is the client environment ready for deployment and going live?
  87. What infrastructure will the client need to host and maintain the solution?
  88. What software will the client need to host and maintain the solution (these two questions will be during Inception, with the help of tech leads)?
  89. Has the user reviewed all required scope to go live/ be deployment ready?
  90. Will the client or client’s target audience need training to use the solution?
  91. Are stakeholders/the movers and shakers/ project sponsors from the client’s side on board with the deployment, go live plan?

    Dotting the I's and crossing the T’s

  92. Does the project’s initially identified success criteria match what will be deployed?
  93. If not, why? Is the client aware and in agreement?
  94. What steps lead to deployment (bug bash/branching/cherry picking)?
  95. Once deployed, what kind of/level of support is needed? How will this need be met?

    dotting i's and crossing t's

    Visualizing a successful, long-term partnership

  96. What are my client’s next steps?
  97. Is there a Phase 2 or a backlog of tasks to be dealt with?
  98. If yes, should that phase be prioritized through an Inception and workshops?
  99. If not, what are the recommendations to use the solution?
  100. Has the development team collected client feedback?
  101. Has the development team given feedback to the client?
I’d like you to keep in mind that, though this list of questions is quite long, it’s still not exhaustive. Honestly, it can never be because the context with which you, the BA are working will play a key role in what is considered relevant and what is not. However, this list of questions should be a guideline that will set you, the team and the client in the right direction.

Disclaimer: The statements and opinions expressed in this article are those of the author(s) and do not necessarily reflect the positions of Thoughtworks.

Keep up to date with our latest insights