Geoff Davis Software Development Leader Software Development at eWater

Goals of our development process Quality products Be able to quickly respond to changes Maintain an efficient collaborative development environment Repeatable process

Properties of Highly Successful Development Teams 1. Frequent Delivery 2. Reflective Improvement 3. Osmotic Communication 4. Personal Safety 5. Focus 6. Easy Access to Expert Users 7. Automated Environment Alistair Cockburn

Properties of Highly Successful Teams Process Practices Team 1. Frequent Delivery 2. Reflective Improvement 3. Osmotic Communication 4. Personal Safety 5. Focus 6. Easy Access to Expert Users 7. Automated Environment

1. Frequent Delivery 2. Reflective Improvement 3. Osmotic Communication 4. Personal Safety 5. Focus 6. Easy Access to Expert Users 7. Automated Environment Properties of Highly Successful Teams Process Practices Team

Properties of Highly Successful Teams Process Practices Team 1. Frequent Delivery 2. Reflective Improvement 3. Osmotic Communication 4. Personal Safety 5. Focus 6. Easy Access to Expert Users 7. Automated Environment

Properties of Highly Successful Teams Process Practices Team 1. Frequent Delivery 2. Reflective Improvement 3. Osmotic Communication 4. Personal Safety 5. Focus 6. Easy Access to Expert Users 7. Automated Environment

Scrum Process – A Sprint

Scrum Process - Roles Product Owner – Represents the stakeholders and is in charge priorities Scrum Master – Facilities the process and removes impediments Development Team - responsible for delivering

Scrum Process - Meetings Planning meeting – at the start of each sprint where the product owner finalises priorities and the team decides how much work can be achieved in the next sprint Daily stand-up meetings – review progress and impediments Review meeting – held at the end of a sprint to review progress against the sprint backlog Retrospective meeting – to look at how we work together. The process and tools we use, and how they can be improved.

Scrum Roles Product Owners Scrum Master (Me) Development Team Source Urban

Development Tools we use TO DO list: Jira Code Sharing - BitBucket (Hg) - Code, tests and test data Automation: TeamCity Monitors code changes Runs a large suite of tests Small scale tests Performance tests Memory tests Automated GUI tests etc..

Our Issue workflow Method for Entering and Managing issues in JIRA

Documentation / Training and sharing Issue tracking Downloading modelling tools User support Forums Knowledge Pool User / Community tools

Stores tests and source code Automatically runs tests, builds installers, and deploys websites Our Automated GUI testing platform Documentation / Training and sharing Issue tracking Downloading modelling tools User support Forums Knowledge Pool

Source Users and Plugin developers can Join in! Jira Code Sharing - BitBucket (Hg) - Code, tests Automation: TeamCity Automate testing Regression tests