A Value Comparison case study of Agile vs Waterfall within a structured PMO framework. Tom Friend Scrum Master

Transcription

1 A Value Comparison case study of Agile vs Waterfall within a structured PMO framework Tom Friend Scrum Master

2 Tom Friend / Experience Industry Experience: Banking, Cable, Broadband, Telecommunications, Mutual Fund, Healthcare, Energy, Federal Sector. Roles: Agile / XP / Scrum, QA, DEV, BA, PM, Federal Contracting Officer. Education: BS Aeronautics from Embry Riddle Aeronautical University. Air War College / US Military. 24 Years US Military Pilot, Retired: 10 Years Navy / 14 Years Air Force Reserve / Flew 7 Different Aircraft. 2 Squadron Commands / 12 Deployments JTAC Ground Combat support for Marines and Army. thomasfriend@hotmail.com About me: 2

3 Agenda Preparation + Testing + Grooming = Value Quick Overview of the Project 1. Proper Preparation and Frameworks from the start» Architecture Foundations» Tools and Coding Standards» Frameworks & building blocks 2. The Value of Automated Testing» J-unit testing / Sonar» Automation Regression» End To End 3. The importance of refining requirements (Grooming)» MoSCoW» Standish Group Features and Functions Agile Value proposition and selecting the right project» DEDB to DAIC comparison = Value added sooner» Profile of a suitable project to realize maximum value» Closing thoughts 3

4 Quick Overview of the Project Project Definition and Team Selection General project items of note Small to Medium project size Greenfield Java Development 3 rd party vendor integration Distributed Team that is new to Agile Offshore 12 hour time difference Preparation Testing Grooming Value Specific team details Team of 12 dedicated resources 5 Developers 3 QA Contractors 1 Product owner 1 Project Manager 1 Business Analyst 1 Scrum Master / Coach 4

5 Proper Preparation and Frameworks from the start Architecture Foundations Frameworks: o Spring framework 3.2.X o Hibernate o JUnit o Log4J o HTML 4.01 o JSTL 1.2 o JQuery 1.7.1, Jquery supported plug-ins o JSON Web Server: Apache 2.2 Application Server: WebLogic Server JDK: JRockit 1.6.0_29 Database: Oracle 11g Enterprise Edition Release bit Webservices: JAXB/AXIS, Spring webservices, Restful 5

6 Proper Preparation and Frameworks from the start Tools and Coding Standards / Unit Testing Build & Release Management Jenkins Maven Code Quality Scans Sonar Unit Testing JUnit 4.11 Code Review IntelliJ IDEA static code analysis Continuous Integration, Integrated Development Environment (IDE) Eclipse (most developers) Idea IntelliJ Strong emphasis on Peer review, Pair programming Performance Testing HP Mercury LoadRunner v11.0 Test Automation HP Mercury Quicktest Professional QTP v11.0 Axe 3.5 Test Management HP Mercury Quality Center Excel Add-in v11.0 Source Code Management Subversion Story, Requirements, Project Mgmt JIRA with GreenHopper Note: Additional Technology Techniques can be found on slides 22 & 23 6

7 Proper Preparation and Frameworks from the start Team Cadence 7

8 Proper Preparation and Frameworks from the start Project 20 Sprints by Functional Theme SPRINT DATE Theme of SPRINT Sprint 1 27-Mar-13 Login Screen / Architecture Standards Sprint 2 10-Apr-13 Main Search /UI Frameworks / Velocity Sprint 3 24-Apr-13 SSO/ Database Setup / Velocity Sprint 4 8-May-13 Account Screen / Offshore Integration / Velocity Sprint 5 22-May-13 Roles / Automated Regression Sprint 6 5-Jun-13 Templates Sprint 7 19-Jun-13 Technical Debt Rolls Rights Slide 22 / 23 Sprint 8 3-Jul-13 Roles Rights Sprint 9 17-Jul-13 Roles Rights Sprint Jul-13 Comments / Notes / SIT Bugs Sprint Aug-13 Vendor Integration / Reports / Sprint Aug-13 Reports Mapping / Vendor Integration Sprint Sep-13 Reports Mapping/ Data Map Vendor Integration Sprint Sep-13 Reminders / Vendor Integration Sprint 15 9-Oct-13 Documentation/ Report views / Vendor Integration Sprint Oct-13 Reports / Training / Vendor Integration Sprint 17 6-Nov-13 Hardware / Training / Vendor Integration Sprint Nov-13 Hardware / FINRA / Vendor Integration Sprint 19 4-Dec-13 Vendor Integration Hardware UAT Sprint Dec-13 Regression UAT 8

9 The Value of Automated Testing Bugs per Sprint 9

10 The Value of Automated Testing Bugs per Sprint Trending 10

11 The Value of automated testing Trending Correlations to Maturity of Automation 11

12 The Value of automated testing Comprehensive Unit, Regression, End to End 12

13 The importance of refining requirements Groomed Backlog / Velocity provides = Delivery Date. 13

14 The importance of refining requirements Velocity focus on what Delivers Value soonest Note: Sprint 10 was low in delivered Story points 14

15 The importance of refining requirements Sprint 10 removed Never and Rarely from Backlog MoSCoW Must have = Always + Often Should have = Sometimes Could have = Rarely Won t have = Never 15

16 The importance of refining requirements Hidden velocity of Grooming 16

17 Agile value proposition and selecting the right project DEDB to DAIC comparison = Value added sooner MoSCoW Must have = Always + Often Should have = Sometimes Could have = Rarely Won t have = Never 17

18 Agile Value selecting the right project Profile of a suitable project to realize this value Standish Group Chaos Report 18

19 Agile value proposition closing thoughts: Preparation + Testing + Grooming = Value Absolute attention to preparation will create an environment of success that breeds more success. Delivering the highest quality product value as soon as possible requires comprehensive testing. The key to managing scope is creating a continual process of prioritization of business value through grooming. When you have a sound foundation, comprehensive test suite, and focus scope to maximum value it is much easier to set and manage value expectations with the business. The temptation with success is to get overconfident and in doing so sabotage your future success. 19

20 Questions? Tom Friend About me: 20

21 Technology Techniques used on the Project Technology UI Speed Transactional Performance Code Reuse Data Management Tiles 3 Yes Yes Yes JPA 2 Yes Yes Yes JPQL Yes Yes Yes DAO Yes Yes Yes Summary of technology to benefits Technology used to attain above objectives Traceability Matrix: TILES 3 Apache Tiles is a HTML template framework base on a composite model of pagelets that are combined to make a final HTML within a JSP Java Server Page. Java Server Pages (JSP) helps create dynamically generated web pages based on HTML, XML, or other document types. Java Persistence API (JPA 2.0) Manages relational data in application using the Java Platform using (JPQL) Java Persistence Query Language. The Java Persistence Query Language (JPQL) is an independent object oriented query language that is part of the Java Persistence API (JPA) specification. Data Access Objects Frameworks (DAO) is an object that provides an abstraction interface to a database or other persistence mechanism. Maven conversions, Maven is a build automation tool used in Java projects. SPRING Security, Is a Java/Java EE framework that provides authentication, authorization and other security features for JAVA applications. 21

22 Technology Techniques used on the Project Detail Detailed benefits of Technology Implemented. The following is the detail of how the above technologies were leveraged. Please Note: this is not a one to one relationship with the items listed on the prior slide Maven conversions Project Infrastructure Foundations: 1.Mitigation of conflicts in dependency management. 2.Simplification of the SVN tagging in the code repository. 3.Creation of multi modules for the project that can be reused. 4.Now leveraging existing frameworks and code in the maven plug-ins. Tiles 3 How pagelets were updated: 1.Configured tilesviewresolver instead of JSP view in spring. 2.Use of Tiles simplified the templates for dashboard, createcase and admindashboard screens. 3.A great deal of the lines of code in jsp is now moved to views.xml. I)js and css imports are now defined in a hierarchical way. II)Tiles 3 optimized the header, menu, and footer content in every jsp. 4.Now all the jsp files have the lines of code optimized now just having only its own specific content. JPA 2 Benefits of greater use of the Java persistence API: 1.JPA2 API has improved persistence over the Hibernate session API. 2.JPA 2 is now part of JAVA EE 6 this is a compatibility benefit. 3.Using the JPA2 EntityManager API, the same Repository layer can be easily switched to other ORM without any changes in Repository. 4.The primary objective of JPA2 features are lot of boiler-plate code is avoided in DAO layer by making use of Predicates which are usable in any criteria query to build the where condition. 5.Make use of Weblogic TransactionManager which provides more features than JpaTransactionManager. Spring Security POC Java framework proof of concept for authentication and authorization: 1.Spring security for SSO login and logout functionality and hence LoginFilter.java can be avoided. 2.Spring security taglibs provided to render the secured content if the user really has the particular permission. 3.Proof of concept was deployed successfully in DEV. 22