I'm Project Manager at my company, and we are trying to use the Agile Scrum methodology to release a software product.
We have a specific milestone (let's call it the creation of a "prototype") that we thought would take all of our departments three weeks to complete. (For the sake of this question I will simplify it and say there are just two departments: Programming and Art.) This milestone was going to be the current Sprint, and we would adhere to all of the usual Scrum guidelines.
However, it was later revealed (mid-Sprint) that there was a piece of the work that would take the Art department an unknown amount of time to complete. They are able to come up with an estimate for how long this type of work would take after being able to do one version of the work within one week. After that one week, they will be able to give an accurate estimate of how long the full amount of work will take, and we can make a plan for how long it will take to reach the milestone/completed prototype.
This presents my problem. Our Programming department does not need any additional time to complete their work for the milestone... they still only need three weeks. However, the Art department needs one week until they can figure out what their full time estimate will be and until we can determine what the "true" end time for this sprint will be.
- Should I make this one week its own Sprint instead, and then have the next Sprint be to hit the milestone prototype once we know how long it will take?
- If I do this option, though, won't that make it confusing for my Programming department because now they have a one week "sprint" with an arbitrary end point in the middle of their work?
- Should I split my team and give them two separate sprints? One for the Art department and a different, simultaneous Sprint for the Programming departmet?
- If I do this option, will I be violating the idea that Sprints are supposed to happen with the full team together? I also worry if it will make our digital to-do lists confusing to look at when "In sprint" for tasks is not referring to the same thing for everyone reading.
What's the best move here? I'm a bit at a loss for how to tackle this and have a decision justified by the Scrum standards. Thanks so much.