Bringing Scrum and High Level Project Management Together
Posted: Tue 13 May 2014 11:25 am
Hello everyone!
It's now been 3 months since we adopted Scrum as the preferred development framework. I can safely say that we are already seeing huge benefits in working this way. However we also have a higher level project flow, which we created not long before we adopted Scrum (a series of 5 project boards, which illustrate each phase of the overall flow). Not all of our project necessarily require Scrum, and some aren't even cross-departmental, but we are looking to transfer some of the gains over to a higher level, applying it as much as reasonable to other areas of the company.
I am fairly new to my roles of both PM Lead and Scrum Master, but I am inclined towards breaking down any non-developmental project into user-stories, in much the same way as we do in Scrum. However, I wouldn't want to run the risk of encouraging a "Waterfall" system, since a variety of stories would depend on different teams (and unlike our Scrum team, we could not expect our design and/or our analysis teams to be cross-functional, for example).
I'm not necessarily looking for an answer or for help, since there are so many variables from company to company. However, if anybody has ever experienced anything similar to my situation, I would be grateful for an insight in how you were able to tackle this conundrum, or even for an opinion on what you think about my "user story" approach.
Thanks all!!
O.
It's now been 3 months since we adopted Scrum as the preferred development framework. I can safely say that we are already seeing huge benefits in working this way. However we also have a higher level project flow, which we created not long before we adopted Scrum (a series of 5 project boards, which illustrate each phase of the overall flow). Not all of our project necessarily require Scrum, and some aren't even cross-departmental, but we are looking to transfer some of the gains over to a higher level, applying it as much as reasonable to other areas of the company.
I am fairly new to my roles of both PM Lead and Scrum Master, but I am inclined towards breaking down any non-developmental project into user-stories, in much the same way as we do in Scrum. However, I wouldn't want to run the risk of encouraging a "Waterfall" system, since a variety of stories would depend on different teams (and unlike our Scrum team, we could not expect our design and/or our analysis teams to be cross-functional, for example).
I'm not necessarily looking for an answer or for help, since there are so many variables from company to company. However, if anybody has ever experienced anything similar to my situation, I would be grateful for an insight in how you were able to tackle this conundrum, or even for an opinion on what you think about my "user story" approach.
Thanks all!!
O.