New team has poorly managed agile/scrum. Should I say something?
I've worked at this company for about a year and half, but recently joined a new team. It's a lateral move, but comes with other benefits and is in a field I'd like to learn more about. The main concern I have with this team is the lack of agile/scrum structure (these might not all be strictly agile/scrum related), even though all development teams in this company use it. My last team had a very experienced scrum master and always kept things on track, but with this team, I'm noticing issues such as: Missing AC or starting to work on a story with no official AC Changing AC mid-sprint Team members point their own stories (no pointing poker or anything similar) In my first sprint, I finished the first story I was working on, then took another one as unplanned. The reason given by my scrum master (in the presentation recap PDF) for not completing the second story was "developer just joined the team." I know that the team technically owns all stories, but that stung a bit, considering I was the only developer to finish their assigned story and I was a new member. Is it my place to bring these issues up and if so, where/when? In the sprint retrospective? To my manager? I've always heard to not make waves unless it's affecting my own work, which technically it isn't.
I've worked at this company for about a year and half, but recently joined a new team. It's a lateral move, but comes with other benefits and is in a field I'd like to learn more about.
The main concern I have with this team is the lack of agile/scrum structure (these might not all be strictly agile/scrum related), even though all development teams in this company use it. My last team had a very experienced scrum master and always kept things on track, but with this team, I'm noticing issues such as:
- Missing AC or starting to work on a story with no official AC
- Changing AC mid-sprint
- Team members point their own stories (no pointing poker or anything similar)
- In my first sprint, I finished the first story I was working on, then took another one as unplanned. The reason given by my scrum master (in the presentation recap PDF) for not completing the second story was "developer just joined the team." I know that the team technically owns all stories, but that stung a bit, considering I was the only developer to finish their assigned story and I was a new member.
Is it my place to bring these issues up and if so, where/when? In the sprint retrospective? To my manager? I've always heard to not make waves unless it's affecting my own work, which technically it isn't.
