Presented by Washington State Administrative Office of the Courts New JIS Development Overview AOC ISD Staff June 10, 2004

c Agenda  Release Planning Process  Roles

c Satisfied Customers/Users  Satisfying customers is most important.  Everything AOC does must tie to business value.  Customers have a right to visibility into the process.  Customers have an obligation to help.

c Release Planning Process  Review White paper  Based on release cycles where new JIS functionality is released every six months.  Scheduled releases occur April 1 and October 1.  Customer-centric process with involvement by representatives from the court community at multiple places throughout release cycles.  Involves coordination by an AOC release management team.

c Release Planning Process  JIS Advisory Committee identifies functionality for the next release based on input from the AOC release management team and court community customers.  Priorities for first release determined by Release Management team.  Current priorities based largely on feasibility for first release effort.  Priority management may require more frequent meetings - phone conf, collaboration software, etc.  Technical constraints, especially bridging to legacy systems, may preclude always working on highest priority.

c Release Planning Process  Enterprise Framework (EF) Teams  Develops a business Model.  Review and define business practices and ensure common practices are identified.  Identify and clarify business practice risks by defining business policies.  AOC development teams, working in conjunction with court customers/users, define and build JIS functionality.  Review Release Cycle chart

c Release Planning Process  Release Plan Overall six-month plan with goals Broken down into three-week iteration plans  Iteration Plan Covers one three-week period Each iteration plan tied to one development team Software is designed and developed a little at a time

c Release Planning Process  Current Release Plan  Six-month plan for October 2004 release  Iteration 1 = May 3 thru May 21  Iteration 2 = May 24 thru June 11  Iteration 3 = June 14 thru July 2  Iteration 4 = July 6 thru July 23  Iteration 5 = July 26 thru Aug 13  Iteration 6 = Aug 16 thru Sep 3  Iteration 7 = Sep 7 thru Sep 24

c Release Planning Process  Review user involvement schedule  Brought in group of users for first week of iteration 2.  Planning the same for next week - June 14

c Software Development Process— Use-Case Driven  Functional requirements are documented as Use Cases.  Use Cases are the basis of project planning.  Use Cases reflect “ever-unfolding story”.  Tie all project activity to real business value.

c Processes—Teams  Teams to Support the Processes  Enterprise framework teams (with customers/users)  Software development/technical teams (with customers/users)  Release management team (AOC team to coordinate overall release planning and interaction between court community representatives and development teams)

c Processes—Teams  Software Development/Technical Teams  Designer  Java Programmers  Tester  User Interface Designer  Customers/Users  Coordinated by a Development Manager  2 teams, 4 teams, 7 teams, a ramp-up

c Processes—Teams  Release Management Team  Release and Client Support Manager  Business Project Managers  Court Business Analysts  Client Project Manager for EF Teams

Washington State Administrative Office of the Courts 1206 Quince St SE P O Box Olympia, WA (360) FAX: (360) Contact Information