Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Project Management 2.0 an agile approach to manage web projects . Francesco Fullone, Ideato.it ff AT ideato.it
Who am I Francesco Fullone aka  Fullo - PHP  developer  since 1999 -  GrUSP  President - PHP and Open Source  Evangelist -...
Part 1: Where we introduce the Project Managment
Project  Management anyone?
Project  Management anyone? The  two golden   rules of a PM.
If something can  go wrong  it will . -- Murphy's Law
Find  good people  and  set them free  to do their job.
The real world  is not that easy .
Project management  practices are a jungle .
R.U.P. (rational unified process)
AKA:  Follow the rules!
Agile.
AKA:  Listen to the team.
Lean .
AKA:  If you don't need it, remove it.
Kanban .
AKA:  What's next?
Total Quality Control .
PERT/CPM.
GTD.
Pomodoro Technique.
...
The  best practice  doesn't exist.
BUT
You should  iterate on  some  good practices to find the best PM  approach for your project!
Part 2: Being Agile , means not...
The  Agile Manifesto
It is based on  some principles .
Individuals and interactions  over processes and tools.
Customer collaboration  over contract negotiation.
Working software  over comprehensive documentation.
Responding to change  over following a plan.
That  means ...
Being agile doesn't mean  being a juggler . Individuals and interactions  over processes and tools.
Good processes are  always  welcomed !
One tool for one task,  don't create noise   in your work.
Collaborating with customer  means not to be his  lover .  Customer collaboration over contract negotiation.
Don't be afraid  to   say  NO!
The customer is part of the team  don't hide informations  and  motivate your choices.
Stop asking for  story points .
Story points  €  ----------------- = -------------- ? Time  Iteration
NO!
Story points are used to  create metrics , after a release,  not invoices .
Embrace the changes,  not the caos .  Embrace the change  over following plan
Focus on application business , don't change your mind too often.
But write at least  the installation guide! Working software  over comprehensive documentation
Part 3: Where  actors  show themselves.
We intended  the PM as the management of different actors  with their own tasks .
In a (web) project  there are many people .
Developers
UX / AI Designer
Marketing
Product owners
Any 2.0  unpaid job
Anyone has  different needs .
All of  them have to communicate those needs  to other members of the team.
And to fulfill these needs there are also a lot of  different tools .
Part 4: Where  tools  are introduced.
On internet you can find lot of PM  verticalized  tools.
BaseCamp .
Easy, with a lot of  features to communicate , nothing to do the  real work .
SourceForge .
Many  tools to manage a community , nothing to manage a budget.
Assembla .
Some “ agile nuts and bolts ” but only for SaaS.
Microsoft Project.
Gantt and resources management  but nothing to open an issue with a customer.
Choosing the  wrong tool  should  create problems  to the team.
Tools  have to help  any kind of  actor  to do its jobs with the less effort.
ie.  SVN integrated with a Bug Tracker  to close automatically issues.
ie. Online  documents revision tool  to help web writers.
Start your project with  easiest  (and unobstrusive)  tool  and then enhance it  if needed .
The best tools  are you and your team .
?
Francesco Fullone ff AT ideato.it skype: ffullone via Quinto Bucci 205 47023 Cesena (FC) info AT ideato.it www.ideato.it
Upcoming SlideShare
Loading in …5
×

Francesco Fullone - Project Management 2.0

5,621 views

Published on

Le slide dell'intervento di Francesco Fullone su Project Management 2.0

Published in: Education

Francesco Fullone - Project Management 2.0

  1. 1. Project Management 2.0 an agile approach to manage web projects . Francesco Fullone, Ideato.it ff AT ideato.it
  2. 2. Who am I Francesco Fullone aka Fullo - PHP developer since 1999 - GrUSP President - PHP and Open Source Evangelist - CEO @ - Nerd and geek
  3. 3. Part 1: Where we introduce the Project Managment
  4. 4. Project Management anyone?
  5. 5. Project Management anyone? The two golden rules of a PM.
  6. 6. If something can go wrong it will . -- Murphy's Law
  7. 7. Find good people and set them free to do their job.
  8. 8. The real world is not that easy .
  9. 9. Project management practices are a jungle .
  10. 10. R.U.P. (rational unified process)
  11. 11. AKA: Follow the rules!
  12. 12. Agile.
  13. 13. AKA: Listen to the team.
  14. 14. Lean .
  15. 15. AKA: If you don't need it, remove it.
  16. 16. Kanban .
  17. 17. AKA: What's next?
  18. 18. Total Quality Control .
  19. 19. PERT/CPM.
  20. 20. GTD.
  21. 21. Pomodoro Technique.
  22. 22. ...
  23. 23. The best practice doesn't exist.
  24. 24. BUT
  25. 25. You should iterate on some good practices to find the best PM approach for your project!
  26. 26. Part 2: Being Agile , means not...
  27. 27. The Agile Manifesto
  28. 28. It is based on some principles .
  29. 29. Individuals and interactions over processes and tools.
  30. 30. Customer collaboration over contract negotiation.
  31. 31. Working software over comprehensive documentation.
  32. 32. Responding to change over following a plan.
  33. 33. That means ...
  34. 34. Being agile doesn't mean being a juggler . Individuals and interactions over processes and tools.
  35. 35. Good processes are always welcomed !
  36. 36. One tool for one task, don't create noise in your work.
  37. 37. Collaborating with customer means not to be his lover . Customer collaboration over contract negotiation.
  38. 38. Don't be afraid to say NO!
  39. 39. The customer is part of the team don't hide informations and motivate your choices.
  40. 40. Stop asking for story points .
  41. 41. Story points € ----------------- = -------------- ? Time Iteration
  42. 42. NO!
  43. 43. Story points are used to create metrics , after a release, not invoices .
  44. 44. Embrace the changes, not the caos . Embrace the change over following plan
  45. 45. Focus on application business , don't change your mind too often.
  46. 46. But write at least the installation guide! Working software over comprehensive documentation
  47. 47. Part 3: Where actors show themselves.
  48. 48. We intended the PM as the management of different actors with their own tasks .
  49. 49. In a (web) project there are many people .
  50. 50. Developers
  51. 51. UX / AI Designer
  52. 52. Marketing
  53. 53. Product owners
  54. 54. Any 2.0 unpaid job
  55. 55. Anyone has different needs .
  56. 56. All of them have to communicate those needs to other members of the team.
  57. 57. And to fulfill these needs there are also a lot of different tools .
  58. 58. Part 4: Where tools are introduced.
  59. 59. On internet you can find lot of PM verticalized tools.
  60. 60. BaseCamp .
  61. 61. Easy, with a lot of features to communicate , nothing to do the real work .
  62. 62. SourceForge .
  63. 63. Many tools to manage a community , nothing to manage a budget.
  64. 64. Assembla .
  65. 65. Some “ agile nuts and bolts ” but only for SaaS.
  66. 66. Microsoft Project.
  67. 67. Gantt and resources management but nothing to open an issue with a customer.
  68. 68. Choosing the wrong tool should create problems to the team.
  69. 69. Tools have to help any kind of actor to do its jobs with the less effort.
  70. 70. ie. SVN integrated with a Bug Tracker to close automatically issues.
  71. 71. ie. Online documents revision tool to help web writers.
  72. 72. Start your project with easiest (and unobstrusive) tool and then enhance it if needed .
  73. 73. The best tools are you and your team .
  74. 74. ?
  75. 75. Francesco Fullone ff AT ideato.it skype: ffullone via Quinto Bucci 205 47023 Cesena (FC) info AT ideato.it www.ideato.it

×