3 ms·
Based on this: >Teams only checked in – wait for it – every three months in a formal schedule review. I listened as Henrich mentioned that the teams complained
by SamuelAdams 7y ago
Based on this:
>Teams only checked in – wait for it – every three months in a formal schedule review. I listened as Henrich mentioned that the teams complained about the volume of paperwork he makes them fill out for these quarterly reviews.
In my experience, embracing agile is an organizational change, not just an IT team change. Product owners and subject matter experts need to be more engaged with their development teams. Not all business folks want to do this: they have their own day-jobs to get to. So when the IT team starts iterating faster, but the appropriate business / project stakeholders do not change their workflow, you get this "AgileFall" combo that just does not really work.
- Ididntdothis 7y agoThat’s exactly how agile got introduced at my company. The scrum training was attended by most devs, only a few higher ranked architects, exactly one level 1 manager. Nobody from marketing, project management or upper management attended and now years later they still don’t understand how Agile is supposed to work. For them it’s something engineers do. So in the end nothing really changed other than words.