Downloaded 18 times
![“if you aren’t ashamed [...] you’ve
released too late”
a better workflow](https://image.slidesharecdn.com/sustainablephpprojects-130330090341-phpapp01/85/Developing-sustainable-php-projects-34-320.jpg)
Uploaded byMichele Orselli
Developing sustainable php projects
The document discusses developing sustainable web projects with PHP. It emphasizes using light weight processes like automating tasks, communicating effectively with stakeholders, and focusing on delivering value through short iterative cycles. The document recommends using tools like Behat for testing, Trello for task management, and continuous integration to regularly deploy updates. It stresses having no assumptions about client needs and designing based on user stories to develop projects in a sustainable way.
More Related Content
Similar to Developing sustainable php projects
Developing sustainable php projects
- 1.
- 2. Michele Orselli CTO@Ideato @_orso_ mo@ideato.it Who am I?
- 3. developing web projectsis hard a lot of web projects fail
- 4. Changing requirements Inconsistent demands Insufficient time or budget http://www.zdnet.com/blog/projectfailures/research-25-percent-of-web-projects-fail/665 a lot of web projects fail
- 5. can we developin a sustainable way? a lot of web projects fail
- 6. light weight processes alot of web projects fail
- 7. already heard aboutthat?
- 8. this is NOTa talk about X where X IN (‘Agile’, ‘Lean’, ‘Scrum’, <insert buzzword>, ...) already heard about that?
- 9. don’t make assumptions howI (we?) develop soft ware
- 10. don’t make assumptions automate how I (we?) develop soft ware
- 11. don’t make assumptions automate communicate how I (we?) develop soft ware
- 12. don’t make assumptions automate communicate code is the easy part how I (we?) develop soft ware
- 13. Thank you! that’s allfolks!
- 14.
- 15. Documentation Sucks! a better workflow
- 16. User Stories FTW! abetter workflow
- 17. AS <role> IWANT <do something> SO THAT <benefit> a better workflow
- 18. there’s no magic abetter workflow
- 19. there’s no magic whole team a better workflow
- 20. there’s no magic whole team focus on value a better workflow
- 21. there’s no magic whole team focus on value comunication vs documentation a better workflow
- 22. no assumptions on whatthe client thinks a better workflow
- 23. prioritization & estimation a better workflow
- 24. no assumptions on what is valuable a better workflow
- 25. GDocs FTW! a betterworkflow
- 26.
- 27. work in smallbatches a better workflow
- 28. work in smallbatches and iterate a better workflow
- 29. no assumptions on whatthe client wants a better workflow
- 30. visualize flow a betterworkflow
- 31. Trello FTW! a betterworkflow
- 32.
- 33. release often a betterworkflow
- 34. “if you aren’tashamed [...] you’ve released too late” a better workflow
- 35. no assumptions on whatthe user wants a better workflow
- 36. short cycles rapid releases iterate let’s do that in PHP!
- 37. from stories totests let’s do that in PHP!
- 38. Behat let’s do thatin PHP!
- 39.
- 40.
- 41.
- 42.
- 43.
- 44. ASSETIC: asset management DOCTRINE:ORM TWIG: templating engine Sf2 components: HttpKernel, Console, Process, ... Zf2 components: Mvc, Db, Authentication, ... ... don’t reinvent the wheel
- 45. don’t reinvent thewheel
- 46. don’t reinvent thewheel
- 47.
- 48.
- 49.
- 50. full-stack frameworks libraries andframeworks
- 51.
- 52.
- 53.
- 54.
- 55.
- 56. no assumptions on the design testing
- 57.
- 58.
- 59. putting it alltogether
- 60. continuous integration putting it all together
- 61. putting it alltogether: CI
- 62.
- 63. PHP is goodenough Wrap up
- 64. Code is theeasy part Wrap up
- 65.
- 66.
- 67.
- 68.
- 69. Thank you! @_orso_ mo@ideato.it Pics Credits Plant: http://commons.wikimedia.org/wiki/File:L4C_small.png Capt Obvious: http://uncyclopedia.wikia.com/wiki/File:Captain-obvious.jpg that’s all folks!