1. Course 2138 Empowering Agile Development With CaliberRM  Jerry D. Odenwelder Jr.  Principal Software Engineer

2. 2 Agenda  Agile Introduction  CaliberRM in Agile Environments  Question and Answers

3. 3 What Is Agile?  Agile Manifesto (http://agilemanifesto.org)http://agilemanifesto.org  Highest Priority is to satisfy customer  Welcome changing requirements  Deliver working software  Working software is the primary measure of progress  Business and Development are Partners not Rivals  Short Iterations (Plan, Design, Develop, Test, repeat)  Methodologies  XP, Scrum, Crystal, Feature Driven Development, dX

4. 4 Agile Values  Individuals and Interaction  Customer Collaboration  Working Software  Adaptive

5. 5 Agile Requirements  User Stories  1…1 or 1…* with requirements  Describes a unit of work that contributes to business value  Created and Owned by the Customer  Meets the P.E.T. criteria  Can be Prioritized  Can be Estimated  Can be Tested

6. 6 Why Use a Tool  Automation  Disaster recovery  Reporting  Traceability

7. 7 Why Use a Tool  Distributed Development  Scalability  Customer is not available

8. 8 CaliberRM Supporting Agile  Light Weight  Expert Client  Cross-Platform/Web Client  Works in your environment  Get the bureaucracy off your back  Document Generation  Reporting  Everyone is on the same page  Central Server  Delphi  Together  JBuilder  Visual Studio  SDK  Eclipse

9. 9 Managing User Stories  A picture is worth a thousand words  Rich Text Descriptions  Attach documents  Speaking the customers language  Glossaries  Manage the story without mangling the story  Requirement Types  User Defined Attributes

10. 10

11. 11 Collaboration  Bring people together when they work remote  Discussions  Making people aware of change  E-mail Notifications  Requirement Creation, Modification, Delete  Posting a Discussion  Baseline changes

12. 12

13. 13 Manage Your Iterations  Shorten your meetings  Requirements Grid for planning and stand-ups  Work Assignments  Responsibility  Compliance  Document Factory  Remembering what was done  History

14. 14

15. 15 Manage Dependencies  Valuable for  Impact of Change  Risk Assessment  Planning  Important Agile Traces  Dependent Requirements  Project Tasks  Model Components  Validation Procedures

16. 16 CaliberRM Support for Dependencies  Support for tracing to  Other Requirements (in any project)  Together Artifacts  StarTeam Artifacts  Mercury Test Director  SCM Tools that comply with Microsoft SCC Specification  Trace Matrix  Trace Grid

17. 17

18. 18 Baselines  Isolate requirements for a release or iteration  Emphasize changes to a release  Support for locking and Digital Signatures

19. 19

20. 20 Security  Ensure that only authorized users can make changes  Supported to UDA level

21. 21 Conclusion  Change is inevitable, embrace it  Requirement Capture and Understanding  Glossary, Spellchecker, Discussion, UI Shortcuts, Requirement Types  Planning and Risk Analysis  Traceabilty, User Defined Attributes  Tracking Progress  Requirement Grid  Post Mortems  Baselines, Digital Signatures

22. Questions

23. 23 Resources (Not Comprehensive)  Agile Manifesto (http://agilemanifesto.org)http://agilemanifesto.org  Addison-Wesley Extreme Programming Series  “Extreme Programming Explained, Embrace Change” by Kent Beck  “Planning Extreme Programming” by Kent Beck and Martin Fowler  Others  “Writing Effective Use Cases” by Alistair Cockburn  MartinFowler.com  The New Methodology  The Agile Manifesto: where it came from and where it may go