| || |
Kanban Cadence - Deployment
I'm working with a new client who has been implementing Kanban methodologies for software deployment. One of the challenges the team has expressed is the goal of a one-week deployment cadence (currently there is no flexibility regarding this time frame and the quality of the software is diminishing, but the cadence is set by an "architect" who has a great deal of authority). Do any of you have experience with longer cadences? I'm more familiar with a 2-week deployment (for features). The team cares a great deal about their work. I'd like to offer evidence that a longer cadence might be beneficial (if that is the case, based on input from you all). Thanks!
I've worked for a company that tried out different cadences between their different divisions. 2 weeks seems to be what we ended up being most comfortable with. Mainly because we didn't like planning meetings every week.
Originally Posted by shannonkb
It's really just a trade off the team has to make. Longer cycles mean less agile, while shorter cycles requires more planning and break down.
Thanks so much for your insight. I appreciate it.