New answers tagged

5

There's a couple of potential solutions: Is it really the case that the team should be generating ideas? Engineering teams are generally responsible for implementing ideas that come from product management, not coming up with the product itself and then creating it. Perhaps you need a PM to design the product so that the team can stay focused on creating ...


7

What I think you lack here is a product owner. Somebody who knows about the product you guys are working on and who can make sure that the user stories that end up in your backlog meet DoR (Definition of Ready). This, of course, does not mean that the team should take what is in the backlog at face value. They do need to challenge it and ask for ...


1

Starve them. Seems whacky but what's killing them is you keep spoon feeding them. Scrum works best when you don't push. The more you manage them the worse this will get. If you have a team of smart driven people all you have to do is lay out a goal and make it clear that they are expected to find work. Just make it obvious that you're watching who's ...


1

Here's how we roll: The PBI: is the requirement aka "the what" is what you talk about with a customer. It's what shows up on the Daily Project Update (DPU) for the sprint..... again because the DPU is customer facing. It's what the customer will talk about and refer in terms of estimates and budget. Might comprise one or more tasks. Is business oriented ...


3

If you are the scrum master and product owner you are a project manager pretending to do scrum. The product owner absolutely has to be someone from the client that is empowered to approve stories, prioritize stories, and accept stories as complete. This is necessary because it forces the client to be involved in the process and there expectations should ...


1

You mention that you are using Sprints, which allows me to assume you are impmlementing an Agile approach such as Scrum. If this is the case, you should have a Product Owner (PO) working with the team to clarify any questions that the time might have, during sprint planning, and throughout the sprint. The purpose of the PO role is to liaise with the ...


7

There may be many stakeholders in the real world, but as far as the developers are concerned, there is only one: The product manager who was selected by the companies involved to have the responsibility that the product created is what the stakeholders need. If that person isn't there or fails to do their job, the project is going to fail. The product ...


3

Close involvement by a primary stakeholder (the "customer representative") is going to be required to make this work. Here's why: Requirements must be accompanied by an acceptance test that, when executed, unambiguously proves that the requirement has been satisfied. If it isn't accompanied by an acceptance test, it's not a requirement; it's a wish. If ...


0

Well, one way or another this comes down to how accurate your estimation of the work involved actually is. And how you manage the risk. I would suggest you have separate processes for minor modifications and major modifications. Minor mods, however you decide to define that, could be fixed price changes, (independent of hours worked). Major mods would have ...



Top 50 recent answers are included