0

Recently, I have taken over the role as a test manager for a company. I am looking at avenues to implement agile. The team does BAU tasks and project work in parallel.

Basically, the work is shared between the team members. We have internal releases which is handled by our in house developers and external releases handled by our COTS supplier. I am planning to implement the following

  1. Bring internal projects and BAU tasks under Agile
  2. All external release and projects to remain waterfall as we depend on other agencies and external vendors.

Does this approach make sense or should I split the team into projects and BAU? Please share your experiences and thoughts.

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
user2852847
  • 15
  • 7
  • 1
    What is *"BAU"*? [Business as usual](https://en.wikipedia.org/wiki/Business_as_usual_(business)) (whatever that means in this context)? – Peter Mortensen Jan 18 '23 at 00:28
  • 2
    You are likely to get more responses to this question in the project management stack exchange: https://pm.stackexchange.com/ – Barnaby Golden Jan 18 '23 at 13:20

1 Answers1

0

I would say the big problem here is, why is there a testing team? Scrum doesn't have testing teams - development and testing is done in the same sprint, by the same team.

If there is a BAU dev team and project dev team, then think about splitting your "testing team" and inject people into each of those teams.

binks
  • 1,001
  • 2
  • 10
  • 26