Comparison Of Pmbok And Scrum

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

4 comments

Comments 1 - 4 of 4 previous next Post a comment

  • + jpartogi Joshua Partogi 2 months ago
    Scrum can also be used in non-software industry. There are some companies that use it in sales and manufacturing
  • + peretti2004 André Peretti 3 months ago
    Oh well, very very good this comparison! Congratulations and thanks a lot!
  • + guest7bd49e guest7bd49e 7 months ago
    Hi .. thanks a lot.. Most the cases in my projects when the PO is really in to the system conceptualisation.. he writes the user stories.. yeah there are times team write them too.. thank you soo much for pointing out.. Wording should be changed slightly there to give the idea about the ownership.
  • + guest31bdf52 guest31bdf52 7 months ago
    These were fine slides. A comment to the fifth row in the Scrum Way (slide 2) is thar P.O writes Userstories. Story points is generatet by the team during Planning Poker
Post a comment
Embed Video
Edit your comment Cancel

15 Favorites

Comparison Of Pmbok And Scrum - Presentation Transcript

  1. ©Thushara Wijewardena ,PMP
  2. NEXT > PMBOK way SCRUM way Management Methodology Management Framework Mange Projects across industries Specific for Software Project Management. “You cant deliver a Bridge part by part to use  ” Project Manger manages the project. Self managed team and the Scrum master together manage the project. Project is split in to various phases One after the other Project is split in to sprints Project Manger define work and prioritize them. Freezed Scope Product owner writes story points and Prioritize them. Freezed Sprints If schedules are not achieved we rebase line them. Sprints can reduce the weight or increase the weight. Planned Project Planned Sprints. Less flexibility to the customer and customer needs to go through a proper change control system to introduce changes More flexibility to the customer with controlled cost Typically weekly or project monitoring Daily scrum is a must
  3. NEXT > PMBOK way SCRUM way EVM calculations are used to monitor the health of the project. Velocity of the Product Burn down and the Sprint Burn down is used to monitor the project. Project Planning will be done in the beginning of the project. Planning will be done at the initiation of the Sprint only for that sprint. Project postmortem meeting will be done at the project closure to review the project and Lessons Learned. End of every sprint there is a Sprint review meeting about the completed sprint. Project is delivered and closed when all the deliverables are met. Project is delivered in iterations. Project is not completed till all the deliverables are met. Customer may stop the project when all his mandatory deliveries are made. Project Estimation history data will be counted based in functionality vs., Avg. Time spent Project estimation history data will be counted based on Average burn rate of the weight points. Issues are listed and Project Manger communicate with the teams Impediments are listed solved and maintained
  4. PMBOK way SCRUM way Project Manager is totally responsible for any project failures Its team work., Team is responsible and some ownership is with the scrum master Project Time is fixed . Anything above is an overrun Product owner is close to the team . He can monitor the causes closely. Customer’s involvement is less Customer is a part of the whole exercise and he present at the every sprint meeting Can apply anywhere any time. Its challenging to commit the required customer involvement when Overseas project outsourcing. Well defined approach for Project Management which covers all the areas of project management up to procurement management Focused on Software Development and delivery only. ( Im reading more on this . I will update this list again ) Risk involved in project transparency Risk is seen in early stages. Project can withdraw with no much damage Done may not be “Done” Every release is a complete “Done”

+ thushthush, 2 years ago

custom

4118 views, 15 favs, 13 embeds more stats

SCRUM Vs PMBOK Comparison

http://projectized.blogs more

More info about this document

© All Rights Reserved

Go to text version

  • Total Views 4118
    • 3693 on SlideShare
    • 425 from embeds
  • Comments 4
  • Favorites 15
  • Downloads 0
Most viewed embeds
  • 224 views on http://projectized.blogspot.com
  • 144 views on http://www.pmtoolbox.com
  • 28 views on http://www.projekt-log.de
  • 11 views on http://www.maxwellanderson.com.br
  • 8 views on http://cltd-confluence.cochlear.com

more

All embeds
  • 224 views on http://projectized.blogspot.com
  • 144 views on http://www.pmtoolbox.com
  • 28 views on http://www.projekt-log.de
  • 11 views on http://www.maxwellanderson.com.br
  • 8 views on http://cltd-confluence.cochlear.com
  • 2 views on http://www.projectized.blogspot.com
  • 2 views on http://translate.googleusercontent.com
  • 1 views on http://74.125.95.132
  • 1 views on http://209.85.165.104
  • 1 views on http://74.125.113.132
  • 1 views on http://localhost
  • 1 views on http://static.slideshare.net
  • 1 views on http://209.85.229.132

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories