Skip to main content
Project Management

Return to Answer

typo
Source Link
Marv Mills
Marv Mills
  • 4.4k
  • 1
  • 20
  • 27

YouYour Scrum transition plan looks good

Here are my suggestions:

  1. Get some training: Any team transitioning to Scrum will struggle with getting stories ready, estimating, release roadmap and so on. So, send some of your key people for training. And ask them to come back and train the rest of the team.
  2. Create feature teams: Not component teams (such as a back-end team and a front-end team).
  3. Plan to keep the teams stable: Teams take time to gel together and become productive.
  4. Making the customer outreach Manager the Product Owner is a good plan: He/she can be the PO for both teams.
  5. You need a strong Scrum Master: For a team transitioning to Scrum you need a strong Scrum Master to establish the process. One possibility you can consider is making the development manager the Scrum Master for both teams. He/she may be good with removing impediments.
  6. Use planning poker for estimation: You may find it a bit slow. But it gives better estimations and team commitment. Also, it gets the team in self-organizing mode.
  7. Hardening week: In my experience teams transitioning to Scrum struggle to get a 'potentially shippable increment' ready by the end of the iteration if they are doing manual testing. Try to introduce automation where possible. In the interim, one way to mitigate this is to have a 'Hardening week' every second or third iteration. The entire team focuses on testing, fixing bugs and getting the release ready.

You Scrum transition plan looks good

Here are my suggestions:

  1. Get some training: Any team transitioning to Scrum will struggle with getting stories ready, estimating, release roadmap and so on. So, send some of your key people for training. And ask them to come back and train the rest of the team.
  2. Create feature teams: Not component teams (such as a back-end team and a front-end team).
  3. Plan to keep the teams stable: Teams take time to gel together and become productive.
  4. Making the customer outreach Manager the Product Owner is a good plan: He/she can be the PO for both teams.
  5. You need a strong Scrum Master: For a team transitioning to Scrum you need a strong Scrum Master to establish the process. One possibility you can consider is making the development manager the Scrum Master for both teams. He/she may be good with removing impediments.
  6. Use planning poker for estimation: You may find it a bit slow. But it gives better estimations and team commitment. Also, it gets the team in self-organizing mode.
  7. Hardening week: In my experience teams transitioning to Scrum struggle to get a 'potentially shippable increment' ready by the end of the iteration if they are doing manual testing. Try to introduce automation where possible. In the interim, one way to mitigate this is to have a 'Hardening week' every second or third iteration. The entire team focuses on testing, fixing bugs and getting the release ready.

Your Scrum transition plan looks good

Here are my suggestions:

  1. Get some training: Any team transitioning to Scrum will struggle with getting stories ready, estimating, release roadmap and so on. So, send some of your key people for training. And ask them to come back and train the rest of the team.
  2. Create feature teams: Not component teams (such as a back-end team and a front-end team).
  3. Plan to keep the teams stable: Teams take time to gel together and become productive.
  4. Making the customer outreach Manager the Product Owner is a good plan: He/she can be the PO for both teams.
  5. You need a strong Scrum Master: For a team transitioning to Scrum you need a strong Scrum Master to establish the process. One possibility you can consider is making the development manager the Scrum Master for both teams. He/she may be good with removing impediments.
  6. Use planning poker for estimation: You may find it a bit slow. But it gives better estimations and team commitment. Also, it gets the team in self-organizing mode.
  7. Hardening week: In my experience teams transitioning to Scrum struggle to get a 'potentially shippable increment' ready by the end of the iteration if they are doing manual testing. Try to introduce automation where possible. In the interim, one way to mitigate this is to have a 'Hardening week' every second or third iteration. The entire team focuses on testing, fixing bugs and getting the release ready.
Source Link
Ashok Ramachandran
Ashok Ramachandran
  • 11.1k
  • 1
  • 22
  • 50

You Scrum transition plan looks good

Here are my suggestions:

  1. Get some training: Any team transitioning to Scrum will struggle with getting stories ready, estimating, release roadmap and so on. So, send some of your key people for training. And ask them to come back and train the rest of the team.
  2. Create feature teams: Not component teams (such as a back-end team and a front-end team).
  3. Plan to keep the teams stable: Teams take time to gel together and become productive.
  4. Making the customer outreach Manager the Product Owner is a good plan: He/she can be the PO for both teams.
  5. You need a strong Scrum Master: For a team transitioning to Scrum you need a strong Scrum Master to establish the process. One possibility you can consider is making the development manager the Scrum Master for both teams. He/she may be good with removing impediments.
  6. Use planning poker for estimation: You may find it a bit slow. But it gives better estimations and team commitment. Also, it gets the team in self-organizing mode.
  7. Hardening week: In my experience teams transitioning to Scrum struggle to get a 'potentially shippable increment' ready by the end of the iteration if they are doing manual testing. Try to introduce automation where possible. In the interim, one way to mitigate this is to have a 'Hardening week' every second or third iteration. The entire team focuses on testing, fixing bugs and getting the release ready.