I have never seen this format of development and testing before. I've always worked in teams where code is tested in the same sprint as this is the most obvious / sensible solution.
Not sure what card system you're using in your team but the majority of card management systems such as Jira or Azure DevOps, allow for developers to add comments. So simply get your team members to add code on what has been done / tested.
If the code hasn't been tested it will sit in the testing column, until it has been simple as. Once it's been tested it can be signed off, or returned to "to do" its a very simple concept of Agile, I'm not sure why your team hasn't been testing in the same sprint (deliberately). Usually the only time the code wouldn't be tested in the same sprint ,is if it was committed towards the end of sprint.
If you have strict deadlines on code deployment, e.g every 2 sprints you deploy signed off code, it just means any un-tested code doesn't make it into that release. If it needs to be in that release, you prioritise development, and testing on that card (even if requires late nights)
Thanks for the reply Grant. Yeah, what you describe is what I see on an agile project, but I have seen more than one of these wagile situations. I know it's not what we want, and I'm just trying to figure out what I might do to help make changes when I see these situations in the future.
And when I say "how to make changes" I don't mean "what process should we really be following". I think I know the answer to that, and you had a good recap. It's really how can I help a large team, with all the existing pressures and deadlines, make those changes while not completely blowing up our cadence.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I have never seen this format of development and testing before. I've always worked in teams where code is tested in the same sprint as this is the most obvious / sensible solution.
Not sure what card system you're using in your team but the majority of card management systems such as Jira or Azure DevOps, allow for developers to add comments. So simply get your team members to add code on what has been done / tested.
If the code hasn't been tested it will sit in the testing column, until it has been simple as. Once it's been tested it can be signed off, or returned to "to do" its a very simple concept of Agile, I'm not sure why your team hasn't been testing in the same sprint (deliberately). Usually the only time the code wouldn't be tested in the same sprint ,is if it was committed towards the end of sprint.
If you have strict deadlines on code deployment, e.g every 2 sprints you deploy signed off code, it just means any un-tested code doesn't make it into that release. If it needs to be in that release, you prioritise development, and testing on that card (even if requires late nights)
Thanks for the reply Grant. Yeah, what you describe is what I see on an agile project, but I have seen more than one of these wagile situations. I know it's not what we want, and I'm just trying to figure out what I might do to help make changes when I see these situations in the future.
And when I say "how to make changes" I don't mean "what process should we really be following". I think I know the answer to that, and you had a good recap. It's really how can I help a large team, with all the existing pressures and deadlines, make those changes while not completely blowing up our cadence.