I've been encouraging my current team to adopt process and workflow changes to be more agile. We have our first retrospective coming up and I'm looking for some advice on how to conduct the retrospective in an encouraging way that influences people to adopt at least some changes.
I've spoken to other devs and our QA guy and the team manager about their thoughts and experiences. So far there seems to be some common agreement on positive changes but also not a lot of experience with Agile process or workflows.
Among the suggestions I think have common ground with multiple teammates are:
- using tickets for assignments, where tickets are prepared with all required information before assignment
- adding more statuses to our JIRA tickets so that anyone can reference a ticket to get the status appropriate to our workflow
- limiting work assignments to the current sprint except for emergencies (emergencies are defined by PMs or team lead)
- setting up more than 1 staging environment for concurrently testing features
Aside from talking to teammates about common ground and their concerns and experiences, how should I go about conducting the actual retrospective with the rest of the team?
Assuming we can keep doing periodic retrospectives, what is some advice for making the best use of retrospectives to push even incremental changes to our process?