Guidewire New 2024.

Guidewire New 2024. Who's uses the acceptance criteria during a sprint? Everyone - Business, analysts, developers, testers and product owners 1. Pre - Inception Activities Goal: Prepare for and Plan for inception Execution Value Consulting Workshop Implementation Workshop Inception Planning Benefit Mapping Workshop Business Trainnig 2. Inception Activities Goal: Confrim Scope and Estimates and Plan the Project Iterations Elaborate Requirements Product and Value Alignment Confirm Scope Plan Project / Sprints Infrastructure Sizing Developer Training Methodology Training 3. Development (1) Activities Goal: Prepare for and Plan for development Execution Plan Sprints Build Solution Demonstrate Results Learn and Revise 4. Development (2) Activities Goal: Enable user stories with technology 5 Stabilization Goal: Confirm the production quality of the stories for deployment Regression testing System/ E2E Model Office / UAT Performance Testing Guidewire Support Transisiton Review and approve 6 Deployment Goal: To enable End users to start using system in production Migrate Data Pilot Deployment Full Deployment Organizational Change managment Support and Success Goal: Realize the value of the production Guidewire system Ongoing customer success program Value realization Business as usual Maintenance Upgrades Learn and Revise Inception (Duration) 1 week sprints Delivery (Duration) 3 -4 Weeks Success Factors for a cross functional team Frequent Communication Co - Located teams Empowered decision making Active business involvement What is SurePath Guidewire Implementation Approach - Optimize scope - Leverage Content - Guided Implementation - Drive Value Which phases in the Guidewire project lifecycle are divided into sprints? Inception Development Stabiilization Which is the typical duration of a sprint in the inception phase? One week During the stabilization phase what is the purpose of the performance testing? Run tests to check how well the system works in anticipated and peak loads During the deployment phase, what happens during the Pilot step? - Allow a subset of users to use the system - Gather feedback - Triage feedback - Implement changes as needed During the support phase who is responsible for monitoring business processes? - Support team What role is the Product Owner (PO)? Drives Value - Key stakeholder representing the voice of the customer - Business authority to make decisions (can delegate to key SMEs) - Shares vision with the development team - Collaborates with the teams to develop and deliver the work - Defines requirements and answers the development teams questions promptly and with authority - Responsible for signing off on user stories and defects - Does not write requirements or test during development Project Manager (PM) Facilitates Progress - Support the sprint team - Facilitate the agile process - Enables self organization - Resolves impediments - Shields outside interferences - Is a participatory leader, not a dictating manager . servant leader Project Manager / Program Managers - Identifies project resources gaps - Coordinates project costs, schedules, and calendars - Manages change control with the PMO - Manages project issues & risk with the PMO - Ensures project quality and timely delivery - Reports status and provides escalation (Is not the person in charge) Subject Matter Experts (SME) - Define business objectives and future state processes - Paricpate in requirements gathering sessions - Review and help refine process flows, use cases and system requirements - Answer questions from business analysts or technical team members about desired system functionality Team Members - Provide cross functional knowledge and expertise - Commit to completing backlog items selected for the sprints - Communicate blockers as early as possible Business Analyst (BA) - Teams with end users to understand business requirements - Acts as a a liaison with all stakeholders to ensure cleat communication between business and technical groups - Assits with funcational requirements and workflow docs - Work closesly with developers and testers during sprint execution so the right features are built and functions as a the business needs - Always focused on demostrating value for the end users - Demo to PO for approval - Document business requiremnts including high level process flows, business rules forms and doucments and typelist values Technical Business Analyst - Coordinate all technical requirements related to guide wire products , customer source systems and integrations - Documents gaps and integration, and assists in the creation of design doucments - Provide impact analysis of the downstream systems - Work closely with developers and testert during the sprint execution so the right features are built and function end to end throughout all impact systems - Document transformation and cleansing rules ( example: Data migration) - Produces mapping documentation (example: document production) Developers - Work with the Business (BA/SME) to understand and develop technical requirements - Responsible for creating design documentation - Writres code to configure the application or integrate it with other applications/ systems - Support test activités during sprint execution to ensure a high quality, working piece of software is delivered - Executes unit testing - Resolves defects - Conducts peer code reviews - Reviews test plans and test cases Quality analysis (QA)