Loading Profile...
Sprint view across projects for shared resources
Would be nice to be able to have a view of all my tasks across all project sprints. We have employee project sharing and some of the developers work part time on projects and thus go across different projects. Now they will have to look at the different projects to see there tasks
I’m confident
5
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has this under consideration.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?This would be very useful! Our company tracks each modification through its own project (for invoicing, etc). This means that a user will have tasks from several projects during each sprint. To view all my tasks during a sprint would be very useful.
I’m happy
-
Inappropriate?What are the odds of us getting this feature? -
Inappropriate?We'll consider that, though I'd advise against doing this in Scrum as a matter of principle. Scrum is about a team that is focused on a common goal. It is hard to be focused on a common goal with your colleagues if you are on more than one team at a time and everyone has to context switch between projects many times a day. In fact this approach must be hurting your productivity - I recommend you to get on one of Ken Schwaber's or Jeff Sutherland's "ScrumBut" presentations. If you have to do what you do for business reasons, then Scrum might not be the method for you.1 Comment
Add a comment
This is one of the best points
-
We are working on parallel releases of the same product, each one with its own backlog.
Another situation: I think that our current days economic reality is adding pressure to IT budgets all over the globe. Even if that's not the case, many of us work in companies where IT and soft. devel. is not core. In either case, one has to decide between many unexpensive, not so bright developers, and a few bright ones. Option 2 forces companies to share teams between projects. And Scrum may, even so, be a nice framework for Project Management. -
Inappropriate?Not all of us have jobs with single projects that can take the length of a sprint and not all of us define projects the same way. Even with 1 week sprints I can't allocate a user to one project. I have members that get shifted between one project and another practically on a daily basis. They're specialists that work on multiple projects. The reality of it is that we all work on one project which is the internal software of our company but we break it up into subprojects. Bananascrum gave us something that we've been unable to properly manage with our excel sheets, the easy manipulation of projects. The only drawback we got from it is one that seems simple enough to fix, a view across projects.
Now for your other comment which I would normally take personal offense to except that I've been practicing SCRUM for too long to not know that ScrumBut happens eventually to all teams as they get comfortable. We've been using SCRUM for years, when we started the only documentation we could find was a PDF from Linda Rising (still have it). Since then we've bought the books and read the articles, well as much as you can for such a simple process. Every now and then we take a step back and start our process over with 1 week sprints and more gestapo approach. That said we're pretty comfortable with our process and we're definitely Scrum and not ScrumBut (at least we are this week).
Remember, purists are best left in the waterfall world :)
So how about it, you going to give us our little feature...we'd be glad to code it for you if you wanted?
I’m amused
-
Inappropriate?Dear Lior, I don't see why you should be personally offended even if we differ in opinion on how this or that methodology should be applied. In any case my intention was not offending you but rather advising you. I still believe with business situation that you have you should consider other methods, for example Kanban, but of course this is your choice what to do with your projects and your team.
Now, going back to Banana Scrum - implementing a cross project view is not as easy as it may seem. Projects are the fundament of the current data model and a consequence of one of the basic design assumptions. Changing that would require lots of work, also there would have to be a special view for this kind of thing. We'll consider addressing this, but it won't be high on the priority list because I feel most users don't have this need.
Still, maybe you can live with the system as it is by using one single backlog and applying tags to differentiate between projects you use. I don't know if you tried the tag mechanism, but it allows selective display and sorting of items within a tag. Hope that helps.
EMPLOYEE
