Alert while Injecting CI/CD for your Scrum Team
It’s an essential for modern organizations to adapt Agile Methodologies in their development to match up the fast paced changes in customer needs.
In quest of achieving this goal, most orgs start their journey with Scrum Practices to shorten the development cycle for delivering small outcomes so that they reach out to market faster & get the valuable customer feedback quicker.
In some time they understand from their Tech vertical that there’s a lot of manual effort in building the feature & getting it to production & orgs start their journey on DevOps path for Continuous Integration & Continuous deployment.
& the FUN begins….
Where things go wrong…
Once orgs start implementing the DevOps channels & sets up the advance CI/CD tools & techniques, things become too much faster.
With current era of cutting edge technologies in CI/CD tools one can easily get to achieve the entire pipeline with capability of doing a production release everyday. And here many orgs falls in the trap.
Team gets excited with capability of frequent releases & start delivering the outcomes within a Sprint. That’s where it breaks the Scrum Framework.
Org needs to understand & adhere to scrum practices.
Once a team decides on Sprint Goal at the start of the Sprint , it should be achieved by DoD(Definition of Done) in sprint & it should be showcased at Sprint Review , Approved by Product Owner & then it should hit the CI/CD pipeline (Probably in Next Sprint)
In against of this, most of the orgs ends up in a Kanban Situation.
Teams keep on developing stories in Sprint & keep on releasing through CI/CD pipeline within same sprint only.(Even if Sprint Goal is not achieved) This greedy behavior eventually makes either Team velocity decrease or compromising the Sprint Goals or dismantling the cross functionality of team.
Teams should understand that, they should leverage the capability of releasing product increments Everyday. But the features which are achieved as Sprint Goals from Previous Sprints, Reviewed by product Owners & most importantly considered as an additional effort/estimated for the current sprint.
IMO , Scrum should be wrapped around “Developing the product increments” & post that it should enter in CI/CD Pipeline.
Open for other views.
