4 ms·

I’m not sure I understand how they interact. My teams have always continued to practice continuous delivery totally independently of sprint boundaries - that is

• wirrbel 8y ago
  Yes, that's how it should be and basically it sounds like you are then already doing a Kanban style working mode (and what purpose does the sprint rhythm than serve)? Scrum by the books usually implies that releases happen after the po or the customer has accepted the increment at the sprint review.
  • matwood 8y ago
    > (and what purpose does the sprint rhythm than serve) I find a good sprint rhythm stops the constant task shuffle. When business knows the dev team is mid-sprint it forces them to think about priority. We do CI/CD, and only big items (in reality UI/UX changes) wait until a sprint review to go out.