How PO and Scrum Team deliver the product on time compare to Traditional Project Management
I'm just studying the scrum one weeks now I have a question is there any way to help PO and development team deliver project on time? As we know every project have timeline and in scrum PO is responsible for managing and prioritizing the product backlog, development team decide what can be done in this sprint. If we don't consider the overtime is there better way to help PO and development to catch the timeline? whether PO should emphasis the project progress in sprint plan meeting?
Hi wen peng,
I assume by delivering the project on time you mean you have a fixed scope, fixed deadline and fixed costs.
If you need to do that, Scrum is not the right tool. You may want to use the PMBOK and a PMI-certified project management professional (PMP). A predictive model works for projects which are relatively simple (e.g. for a software roll-out).
If you want to develop a product, you are probably in the complex area, where predictive models don't work. Here you need an empirical process framework like Scrum. But you have to accept that there is no "delivering project on time". There is only "delivering the maximum value for the minimum cost while reducing the risk".
Value is the PO's accountability, the SM helps the team to work productively and efficiently (costs) and the team reduces the risk by delivering a potentially shippable increment each sprint, so the risk is reduced to one sprint.
I think you are not alone with your request concerning the possibility to combine PM and SCRUM.
Unfortunately it won't work. SCRUM got an completely different base. That's why there are lots of conflicts and problems to solve if a company tries to implement SCRUM.
> I'm just studying the scrum one weeks now I have a question is there any way to help PO
> and development team deliver project on time? As we know every project have timeline
Scrum teams use timeboxes, not timelines, and it isn't projects that are delivered...products are. This is why sprints are timeboxed and a potentially releasable increment should be available by the end of each one. The best single thing anyone can do to assist delivery is to promote this incremental release of value.
This allows the PO to achieve an early return on investment, reduce the cost of delay, and to mitigate delivery risk. So in Scrum value is to be found in delivery, not in following a predetermined timeline or schedule. Ken Schwaber summarized the Scrum position on this in the following interview yesterday: http://www.geekwire.com/2014/5-questions-ken-schwaber-co-creator-scrum/
Thanks all. It's a wonderful place to learn scrum.
Hi Wen Peng,
The team can deliver on defined time but at the same time they can not deliver all of the defined scope. Fixed time and fixed scope does not work with Scrum. PO ensures that the highest value items is always on the higher order and remove irrelevant items, and the dev team ensures that they always deliver DONE software (according to the definition of done) every Sprint.