Closing the Agile Loop: Continuous Feedback. Darryl Bowler, CollabNet, Sr. Systems Architect Brian Dawson, CollabNet, Sr.Technical Consultant

Transcription

1 Closing the Agile Loop: Continuous Feedback Darryl Bowler, CollabNet, Sr. Systems Architect Brian Dawson, CollabNet, Sr.Technical Consultant

2 Presenters Closing the Agile Loop Webinar Series Darryl Bowler, Senior Systems Architect, Services, CollabNet With more than fifteen years of IT experience, Darryl Bowler leads the consulting services business for CollabNet Lab Management, delivering high-value virtualization and test lab automation consulting services to major enterprises. Darryl is an accomplished senior systems architect, specializing in software development methodologies, virtualization, and cloud computing, combined with application lifecycle management and agile best practices. Brian Dawson, Senior Consultant, CollabNet As a Senior Consultant at CollabNet, for 5 years Brian Dawson has helped software development organizations large and small improve the Application Lifecycle Management process through the use of TeamForge. Prior to CollabNet, Brian spent 12 years in software development. Ten of those years were spent at Sony Computer Entertainment where he worked as the Director of Tools and Technology and oversaw the development and deployment of TeamForge as a worldwide collaboration portal. 2

3 Agenda Feedback and Continuous Integration Feedback and Continuous Delivery Guidelines for feedback Feedback Mechanisms Feedback and the Delivery Stages Integrating with Agile ALM 3

4 Feedback Or more specifically Information produced during the software development process, provided to the process participants and used to improve the product of that process. 4

5 Feedback and Continuous Integration Continuous integration is fundamentally establishing process to provide feedback early and often Fail fast so problems can be found and corrected early CI feedback is developer focused Coding and architectural issues Failed builds Failed unit tests Continuous integration (CI) is a software engineering practice in which isolated changes are immediately tested and reported on when they are added to a larger code base. The goal of CI is to provide rapid feedback so that if a defect is introduced into the code base, it can be identified and corrected as soon as possible. Unknown 5

6 Feedback and Continuous Delivery Continuous Delivery extends the CI process from build to include test and deploy phases Ensure fluid coordination and communication between Mangers, Developers, Testers, and Operations Fail fast ( as possible) so problems can be found and corrected early as possible Appropriate feedback must be communicated to all process participants Build status Acceptance test results Deployment status Smoke tests results Operational issues Continuous delivery of software needs processes that encompass the entire delivery process, from concept to use. Unknown 6

7 Feedback and Continuous Delivery Continuous Feedback Provides visibility for the entire team into what is being delivered so that Issues are identified early Collective confidence in the release is achieved Should be implemented early in development of the CI/CD process Goes hand-in-hand with end to end traceability Can include ALM activities such as story and test case development. Team communication is not replaced by automated feedback - Continuous Delivery Humble & Farley - Addison-Wesley 7

8 Poll Question #1 Which SCM tool are you using? 8

9 Guidelines for Feedback Feedback must be Fast and early Visible and accessible Actionable And most importantly Acted On! Feedback should not be Too much Too late Too little 9

10 Guidelines for Feedback Acting on the Feedback Feedback is only useful if it is acted on The team should develop rules for handling various types feedback of feedback Broken build Do not check-in Stop and work and correct Drop in code coverage Do not introduce new changes until test code coverage exceeds threshold Failed smoke test in production Rollback to previous version and correct immediately. The team must be held to those rules Make sure event, action and result are public remember Automated feedback does not replace the need for team communication! Responding to feedback and resolving issues quickly and correctly requires the team communicates. 10

11 Feedback Mechanisms Asynchronous or Pulled Commit Logs Dashboards Pipeline View VCS Tags Deployment reports Code metrics Synchronous or Pushed Instant Messaging Social Media IDE Monitors RSS ALM Platforms (i.e. TeamForge) Extreme Feedback Lava Lamps Orbs Rocket Launchers Large Screen Displays 11

12 Feedback Mechanism Examples Eclipse Build Monitor Pipeline View Extreme Devices TeamForge Tracker, File Release and SCM w/monitoring 12

13 Poll Question #2 What feedback mechanisms do you use? 13

14 Feedback and the Delivery Stages Commit Stage Commit notifications Build status Build results Unit test results Code quality Testing Stage Non-Functional Tests Results Acceptance Test Results Manual Test Results (via ALM or tracker integration) Deployment Stage Stage Smoke tests Production Monitoring Deployment report - Jez Humble and the planning stage. 14

15 Integrating with Agile ALM Agile ALM begins with the planning stage Downstream activities are driven by needs determined before coding begins Traceability and feedback can start here 15

16 Integrating with Agile ALM TeamForge is an example of an ALM platform which supports the process and its feedback end-to-end 16

17 17 Integrating with Agile ALM

18 Integrating with Agile ALM Capture the output from the process stages.. 18

19 Integrating with Agile ALM Update the team and the business 19

20 Poll Question #3 Which issue trackers are you using? 20

21 Summary Feedback is fundamental to Continuous Integration and Delivery Feedback should be fast and as early as possible Feedback should be actionable Feedback must be acted on Traceability is required to support actions based on feedback Tailor your solution to fit your team If an existing solution doesn t fit, create one that does Feedback should encourage, not discourage Team communication is as important as automated feedback 21

22 Questions? 22 Copyright 2008 CollabNet, Inc. All Rights Reserved.

23 23 Copyright 2008 CollabNet, Inc. All Rights Reserved.