Timeline for How to manage a schedule across multiple PMs when using a single team for both development & support?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 24, 2015 at 19:06 | comment | added | Superunknown | Thanks for the input, I spoke with the team and we've already made a start on creating a high-level schedule for the next few weeks. We're actually going to trial splitting the teams in order to reduce the amount of distractions, and have a resource/schedule planning meeting every week. | |
| Nov 24, 2015 at 19:00 | vote | accept | Superunknown | ||
| Nov 24, 2015 at 9:15 | comment | added | TTKDroid | It depends on how often things are likely to change and for how long resources can be committed. You may have an initial resource plan and have monthly reviews with other PMs/SDMs to refine/adjust/react/adapt to current reality. Unfortunately the shared resource model demands more planning and management to work properly. | |
| Nov 24, 2015 at 8:57 | comment | added | Superunknown | Thanks for the reply, your comments certainly mirror some of the discussions we've been having internally. From your experience, how far ahead should we plan? Should this just be high-level whereby we're focusing on the project and the team member, rather than at ticket level? We used to work in sprints, but we turned to Kanban in the end because it allowed us to be more flexible with priorities - sadly, more often than not sprint planning became obsolete due to an urgent support query, or customers changing their minds. Kanban certainly seems a better fit for how we operate. | |
| Nov 24, 2015 at 1:05 | history | answered | TTKDroid | CC BY-SA 3.0 |