Retrospective tools when new members in the team
Hi all,
I have a really great team with five members. Now it looks like, from another team we get two people, they become part of my team. They come from a team which has lots of big problems about agile, software, management and team members.
We will go out for a day and I would like to organize a "big-retrospective" event, when everybody can talk about the problems and behind them back.
Do you have any idea what type of retro should I organize?
Did your team of five people request the inclusion of these two new members? Have they chosen to self-organize this way? It sounds like this move is not quite under their control, and that it has taken you a bit by surprise.
This decision was made by management. Nobody from the team was not included in it (neither me)
The new two members have own product. It looks like there are two different products, two different programme languages, but from now they are one "team".
I am a bit afraid of this situation. First of all I would like to achive the new members can behind back their old problems and their previous bad experiences.
It looks like there are two different products, two different programme languages, but from now they are one "team".
The existence of a team is evidenced by teamwork. It is not evidenced by management or anyone else asserting that there is "one team".
My advice is to put transparency over the situation. If there are two different products then the work should be captured and prioritized in two separate product backlogs each with a clear Product Owner.
Now encourage the "team" to self-organize around the work. It's possible that two viable teams might emerge. If only one team is viable, then perhaps they can alternate between products in different Sprints and gradually cross-train over time.