Social project management

625 views

Published on

Social project management

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
625
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
11
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Social project management

  1. 1. social project management everything small is big again
  2. 2. so, social project management huh!
  3. 3. what's the fuss about?
  4. 4. the 'social' revolution
  5. 5. changing the way we do many things
  6. 6. a new way of 'doing' projects..
  7. 7. well, not really, new
  8. 8. it's just that they're being taken A LOT more seriously these days
  9. 9. limited planning no documentation diy (small teams)
  10. 10. multiple skillsets small budget release asap
  11. 11. what was once a 'hack' is now an accepted methology
  12. 12. so, social project management
  13. 13. what does it look like?
  14. 14. small teams
  15. 15. smart, motivated people
  16. 16. limited planning
  17. 17. a clear vision
  18. 18. minimal scope
  19. 19. small projects
  20. 20. multi-skilled teams
  21. 21. fast pace
  22. 22. rapid release
  23. 23. alpha, beta
  24. 24. feedback
  25. 25. responsiveness
  26. 26. iteration
  27. 27. is this really so new?
  28. 28. there are not-so-new alternatives
  29. 29. agile
  30. 30.   individuals and interaction over processes and tools working sofware over comprehensive documentation customer collaboration over contract negotiation respond to change over following a plan while there is value in the items on the right , we value the items on the left more agile software development
  31. 31. shorter development cycles, iteration, end user involvement, multi-disciplinary teams
  32. 32. compare and contrast with 'project management 1.0'
  33. 33. large scale projects
  34. 34. top down
  35. 35. centralised control
  36. 36. authoritarian environment
  37. 37. implied structure
  38. 38. limited communication to team and end users
  39. 39. over complex tools
  40. 40. rigidity of tools
  41. 41. local access to information
  42. 42. gantt charts
  43. 43. managed with a guesstimation paradigm
  44. 44. many stakeholders
  45. 45. escalating requirements
  46. 46. complex dependencies
  47. 47. risk registers
  48. 48. mammoth teams
  49. 49. scary and crazy budgets
  50. 50. horizon and beyond timelines
  51. 51. expected failure
  52. 52. why do these projects fail?
  53. 53. first, do they fail?
  54. 54. oracle, peoplesoft, sap, accenture, ibm global services
  55. 55. the 1.0 'large scale', top down project approach fails spectaculary all the time
  56. 56. except they don't *officially* fail. because we update the gantt chart as we go. we move the goal posts
  57. 57. but why?
  58. 59. traditional project managment doesn't match the way we work
  59. 60. that said
  60. 61. social project management projects *also* fail all the time
  61. 62. for different reasons
  62. 63. usually because it just wasn't such a great idea
  63. 64. or the implementation was completely wrong
  64. 65. or the audience doesn't exist yet.
  65. 66. but it doesn't matter
  66. 67. because they're smaller and faster with less investment
  67. 68. dust off, learn from the mistakes and move on
  68. 69. ok, so what's all this *social* stuff got to do with it? 
  69. 70. Project Manager Client Development Analyst Design Senior Dev Dev Dev Dev Stake-holder UX Consultant UI Designer Stake-holder Stake-holder Stake-holder Test Lead Test Tester Tester
  70. 71. new toys
  71. 73. tasks, milestones, documents , meetings, wiki, chat, bug tracking
  72. 74. 100% securely online, 24/7/365
  73. 75. encouraging and promoting faster time to market
  74. 76. through online social collaboration
  75. 77. contact adapted from the original by lisa reichelt (lisa.reichelt@gmail.com) w: turinproject.com t: @turinproject.com fb: bit.ly/turinprojectfacebook

×