• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Scrum and Project Management
 

Scrum and Project Management

on

  • 8,967 views

A presentation given for the PMI community in November 2008. The presentation shows the main difference between traditional and agile project management.

A presentation given for the PMI community in November 2008. The presentation shows the main difference between traditional and agile project management.

Statistics

Views

Total Views
8,967
Views on SlideShare
7,497
Embed Views
1,470

Actions

Likes
13
Downloads
702
Comments
0

11 Embeds 1,470

http://www.techbaba.com 690
http://pm-blog.com 648
http://www.slideshare.net 43
http://scrum4you.wordpress.com 29
http://borisgloger.com 27
http://macaubas.com 22
http://elsewhere.posterous.com 4
http://meikelkay-pmlog.blogspot.com 3
http://static.slidesharecdn.com 2
http://www.lmodules.com 1
http://translate.googleusercontent.com 1
More...

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Scrum and Project Management Scrum and Project Management Presentation Transcript

    • presents Scrum and Strategical Project Management First Things First! From the Product Vision to the Product Result Boris Gloger, 2008 1
    • 2 Yahoo Chief Product Owner – “Scrum is faster, better, cooler! It’s the way we first built software at Yahoo, yet is scalable to large, distributed, and outsourced teams.”
    • The Product Owner is key! working together for innovative results 3
    • Product Manager A Project A Team A Why Change? Product Project B Team B Manager B No Focus Product Project C Release Team C Manager C Manager Release X No Visibility No Predictability Product Project D Manager D Team D Product Manager X Project X Team X No Dedication Getting Lost? getting lost? working together for innovative results 4
    • What is the basis for most project plans? 5
    • WBS 6
    • What is the lowest level of a WBS? 7
    • Tasks or Activities, or? 8
    • Strategic vs. Tactical 9
    • If the lowest level of our project plan is based on activities, what kind of project plan do we get? 10
    • TACTICAL PLAN 11
    • All estimates, all assumptions -- so all planning (= thinking) is based on a highly exible and variable basis 12
    • IN SCRUM OUR LOWEST LEVEL OF PLANNING BEFORE THE DOING IS STRATEGICAL!! 13
    • The agile planning basis is a ... 14
    • FB S eature reakdown structure 15
    • We call it a Product Backlog A list of items we want to deliver 16
    • The Product Increments will be delivered based on : 1. Sorting 2. Size 3. Velocity of the team Sprint Sprint Sprint time Release source -- objectbay, andreas wintersteiger 17
    • Scrum & Business Scrum is highly business and product AND THE oriented. Business get a real live information of WINNER IS project status on daily basis ... Every 30 days a product increment is ready and can be used. Business working together for innovative results 18
    • “There is not Business Involvement! such thing as a A prioritized Product Backlog! A dedicated Product Owner! free lunch” Robert A Heinlein, The Moon is a Harsh Mistress First Things First! IT IS HARD WORK! working together for innovative results 19
    • Product Vision A Vision is a clear picture that evokes an emotional attraction. The Product Owner creates the product vision He shares this vision with his team He re nes this vision with the team working together for innovative results 20
    • Create the Product Backlog The Product Owner creates and maintains the Product Backlog! Never show up to a Sprint Planning without estimated and prioritizes Product Backlog. Make it public to the organization! working together for innovative results 21
    • Prioritize the Product Backlog First Things First! Prioritization based on business value Use your tools and your common sense! working together for innovative results 22
    • Work on Daily Basis with Team members! Clarify Ideas and Vision Clarify Requirements JOIN THE DAILY SCRUM! Do Decisions quickly! Re-prioritize if the team runs into problems working together for innovative results 23
    • Review the Product Review the product give timely feedback a) during Sprint b) in Sprint Review working together for innovative results 24
    • Call the Estimation Meeting Fibonaci! Get sizes from you team Give them the chance to get an insights into the new ideas working together for innovative results 25
    • Create Release Plan Build the release plan 3 month ahead! Work hard on meaningful Sprint Goals! Work with all parties to create one Releaseplan! Involve Team to create Release plan working together for innovative results 26
    • Sprint Planning Brief your team in the meeting! Know exactly what you want! Be clear when you communicate! Negotiate Goal and Scope! working together for innovative results 27
    • The Product Owner is key! working together for innovative results 28
    • boris gloger contact me at: schwarzwaldstraße 139 skype: borisgloger 76532 Baden-Baden email: boris.gloger@borisgloger.com Germany web: http://www.borisgloger.com copyright by boris gloger, 2008 29