Hey Ryan, Todd - It's great to listen to your YDS videos. Thanks for sharing your knowledge and experiences. Can you guys please make a video about "How to measure context switching?" This will come in handy for all agile practitioners.
This is a problem even in just projects that are more Waterfallish. I had two projects spin up, in intensity, at the same time. I was so busy, that I couldn't even remember the passwords to log into my computer the next day. It is really difficult to manage effective communication and teamwork when there are people supporting multiple projects.
I'd be curious to know what constitutes a "project"? Is feature work and bug fixes different projects? How do we mitigate context switching (Sprint protector maybe...)?
I work in the agency world so a "project" is literally an entirely different project with it's own Job number and it's own code base. I would say a project could also share a codebase but have it's own unique Epic's with a requirement for domain knowledge of that project. Bug fixes I would consider maintenance or QA on whatever project those bugs were introduced during.
Hey Ryan, Todd - It's great to listen to your YDS videos. Thanks for sharing your knowledge and experiences. Can you guys please make a video about "How to measure context switching?" This will come in handy for all agile practitioners.
This is a problem even in just projects that are more Waterfallish. I had two projects spin up, in intensity, at the same time. I was so busy, that I couldn't even remember the passwords to log into my computer the next day. It is really difficult to manage effective communication and teamwork when there are people supporting multiple projects.
Do you have any tips for people working in multiple projects. We're a small team doing a mix of maintenance and new development for multiple projects.
I'd be curious to know what constitutes a "project"? Is feature work and bug fixes different projects? How do we mitigate context switching (Sprint protector maybe...)?
I work in the agency world so a "project" is literally an entirely different project with it's own Job number and it's own code base. I would say a project could also share a codebase but have it's own unique Epic's with a requirement for domain knowledge of that project. Bug fixes I would consider maintenance or QA on whatever project those bugs were introduced during.