The document provides an overview of the Alfresco engineering team and its key decision-makers, emphasizing a collaborative approach to software development. It highlights the importance of early validation of ideas, shared ownership among engineers, and a structured backlog for managing features and maintenance tasks. The Agile development methodology, including scrum teams and a focus on innovation, is also discussed.

1. Alfresco Engineering
David Webster
Staff Software Engineer

2. The code doesn’t write itself

3. Decision Makers
• John Newton
– Chairman & CTO
• Doug Dennerline
– CEO
• Thomas DeMeo
– VP Product Management
• Paul Holmes Higgins
– General Manager,
Activiti

4. Product Development
• Mark Heath
– VP Product Development
• Brian Remmington
– VP Engineering
• Greg Melan
– System Architect

5. Follow The Sun Development

6. Records Management

7. 3-in-a-box

8. Flows and Wireframes

9. Validation
• When: Early & frequent
• Who: Existing customers & prospects

10. Engineers: Task Breakdown

11. Building the Backlog
New features
Maintenance
(bug fixes) Innovation
Backlog

12. Bugs

13. Development Scrum Teams

14. Nightwing and Flamebird

15. Release Velocity

16. Git

17. Where/When/How

18. Maidenhead Office

19. Work in Progress

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. 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. Alfresco Engineering
David Webster
Staff Software Engineer