Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

BeeCon 2016 Alfresco Engineering lightning talk

151 visualizaciones

Publicado el

A quick review of how Alfresco Engineering (the RM development team specifically) work (current as of April 2016).

Publicado en: Software
  • Sé el primero en comentar

  • Sé el primero en recomendar esto

BeeCon 2016 Alfresco Engineering lightning talk

  1. 1. Alfresco Engineering David Webster Staff Software Engineer
  2. 2. The code doesn’t write itself
  3. 3. Decision Makers • John Newton – Chairman & CTO • Doug Dennerline – CEO • Thomas DeMeo – VP Product Management • Paul Holmes Higgins – General Manager, Activiti
  4. 4. Product Development • Mark Heath – VP Product Development • Brian Remmington – VP Engineering • Greg Melan – System Architect
  5. 5. Follow The Sun Development
  6. 6. Records Management
  7. 7. 3-in-a-box
  8. 8. Flows and Wireframes
  9. 9. Validation • When: Early & frequent • Who: Existing customers & prospects
  10. 10. Engineers: Task Breakdown
  11. 11. Building the Backlog New features Maintenance (bug fixes) Innovation Backlog
  12. 12. Bugs
  13. 13. Development Scrum Teams
  14. 14. Nightwing and Flamebird
  15. 15. Release Velocity
  16. 16. Git
  17. 17. Where/When/How
  18. 18. Maidenhead Office
  19. 19. Work in Progress
  20. 20. Points to Remember 1. Early idea validation 2. Engineers own story breakdown 3. Shared ownership (process, code, tests, bugs) 4. No surprises on backlog 5. Innovation, maintenance & features all prioritised on backlog
  21. 21. Points to remember 1. Early idea validation 2. Engineers own story breakdown 3. Shared ownership (process, code, tests, bugs) 4. No surprises on backlog 5. Innovation, maintenance & features all prioritised on backlog
  22. 22. Alfresco Engineering David Webster Staff Software Engineer

×