Hot answers tagged

4

Mark Wallace is correct that this is primarily a people issue not a technology or Scrum-technique issue. Fortunately there are some people-techniques that work to resolve certain sorts of people issues. Your issue here is resolvable. Daniel's answer touches (brilliantly) on the phenomenon here: that different personalities can have wildly different work ...


4

You may have a difficult conversation to have with the stakeholder. To be perfectly blunt, work with no pressure or stress is called a hobby. I don't recommend you lead with that. What might help is this: Agile (and it sounds like Scrum would be particularly helpful) focuses on getting work complete through small increments. You start with a foundation idea ...


2

Great question, and kudos for being concerned enough about the bigger picture to reach out. A team I worked on a couple years ago was in the same boat as you are: great at the day to day but a bit lost when it came to the bigger picture. We found interactive story mapping really helped everyone understand not only WHAT they would work on next, but WHY. ...


2

There are a lot of variables in your situation that I don't know the answer to and so I'll try to keep my suggestions as high-level as I can. Either way, please use them as only a starting point. 5 Levels of Planning First I'd look at the 5 levels of planning. There's a lot of info to look up on this, but the short version is that they are: Vision ...


1

My company recently added a top-level strategic roadmap. It has a separate project for each department (marketing, sales, dev, HR and etc.) and each project has only a few works in it with department head being responsible. Looks like this (not an actual thing):


1

The Vision is the expected end state, especially as it pertains to the business/user/customer facing end state. Simple example: Umbrella or similar product Vision: when walking outside I will be, using a light-weight, easily portable device, protected from sun, rain, wind. Proposal will describe what product or service the contracting organization will ...


1

Mind that Scrum talks about potentially shippable increments (PSI) as opposed to potentially shippable code! Of course you can ship code, but you can ship other things as well. For example, a product-vision document could be a shippable increment. Sprints with the goal do gain insight are often called Exploration Sprints. They are not unusual. In general, ...


1

TL;DR There are often debates between Scrum practitioners about whether to have a Sprint Zero or not. You can side-step the various arguments by redefining what the Sprint Goal will be for the first sprint, and by adjusting expectations of what will be demonstrated in the Sprint Review. Sprint Goal Sometimes, the drive to have a "Sprint Zero" seems like a ...


1

is it OK to have a Sprint 0 with no deliverable code? Remaining true to Scrum framework, the answer would be NO. Can you time-box the Sprint 0? If the answer is no then you would be violating two important factors of Scrum framework, first time-boxing and the second potentially deliverable code at the end of each sprint. As you have mentioned that the ...


Only top voted, non community-wiki answers of a minimum length are eligible