Skip to content

questions to ask when you are a new agile team

Jump to bottom Edit New page
Matthew Hall edited this page Jul 17, 2018 · 14 revisions

If are new to Agile or to using the Scrum Methodology you may be under the impression that the Agile Manifesto or the Scrum Methodology will provide with the answers for how to effectively develop solutions that meet users needs. What you will very quickly realize is that Agile and Scrum only provide you with a structure within which to be successful.

If I can use an analogy, it is like describing how to write a novel. It should have a beginning a middle and an end, you will need characters. You will need to have various story lines that connect within the overarching story and help to achieve the main goal.

However, when you sit down to write it, you find that you stil have to create every line of content in the novel on your own. Agile and Scrum are no different.

Outcomes:

  • What should the outcomes be of having an agile sdlc?

STUDY TOPIC: "Outcomes vs Outputs"

Tools

  • What information shows up on a product roadmap?

STUDY TOPIC: "Product Roadmap vs Release Plan"

  • What sort of documentation would you need to help you achieve success in your role?

STUDY TOPIC: "Living Documentation"

  • What types of tools do want to get more value out of?
  • What tools will the team use to collaborate?
  • What tools will the team use to manage the backlog of user stories?

Process

  • How should the backlog evolve during concept, initiation, and construction?
  • If you could summarize the agile sdlc in 5 bullets points, what would they be?
  • How can your role be supported by an agile sdlc?
  • What processes are you most unclear on?
  • How does service design fit into the agile sdlc?
  • How does behavioural insights fit into the agile sdlc?
  • How does cross team collaboration fit into the agile sdlc?

Governance

  • How can I ensure that people are using the tools that the team has decided to use?
  • What processes could benefit from having a way to measure their effectiveness or ensure that they are followed consistently?
  • Other than the Scrum ceremonies what regular events should the Scrum master be doing?
  • How can or should we ensure that teams are using burn down chart or similar measures to forecast their team velocity, changes to the backlog, and estimate completions dates for an product epic or feature set

CSI Maturity

  • What backlog characteristics provide the product owner/manager with what they need to communicate to their executive that the project is being managed well?
  • How should we measure the maturity of our ability to use the processes and tools?
  • What is the most important thing you would tell to a new team joining the CSI Lab?
  • What can be done to increase the level of collaboration across teams?
  • What interactions with the organization does the Scrum team need to have in order to ensure a successful project?
Add a custom footer
Add a custom sidebar
Clone this wiki locally