IP Deliverer Playbook Briefing session

IP Deliverer Playbook Briefing session. August 2022.

Content. 2. IP Deliverer Playbook – Purpose and key benefits IP Deliverer Playbook - Contents IP Deliverer Playbook - Demonstration User Testing plan Functionality Testing User Experience Testing Roles and responsibility Categorisation of Feedback Next steps Support Questions.

[Audio] Connection - The IP Deliverer Playbook is for everyone in IP whether you are a fresh starter or a seasoned professional. It connects with our people and our daily work. Uniqueness. Playbook is filling in the gap that our users are facing in their work in finding right information ( example processes, procedures, template etc). Playbook is not duplicating any information and directs users to the related resource in business whether it is IMS, DMS, Project pack, ETMS or relevant Sharepoint site..

Home Page Ways of Working Capital Projects Framework Project Management Initiatives.

5. IP Deliverer Playbook. IP Deliverer Playbook. IP Deliverer Playbook.

User Testing plan. Plan requirements Testing type Functionality User Experience Testing participants Functional – Content owners, SMEs from relevant Business area User Experience – Nominated 2~3 staff per branch (Snr Project Manager, Project Manager, Project officer, Engineer) Timeframe Testing took place over two weeks Functionality: 22 - 25 Aug User Experience: 29 - 31 Aug Commitment Approx. 20- 30 mins over the testing period (at own pace) Testing location Testing will be completed performed remotely Equipment and resources Desktop, laptop, tablet Operating system, browser Playbook link Test cases and instructions Support contact Rajeev Tyagi and Monica Benivento Briefing sessions held for testing participants Functionality User Experience Test evaluation / cases Two separate survey developed for users to complete up after going through Playbook Functionality and 2. User Experience.

[Audio] Adam to present. Testing of IP Deliverer Playbook.

[Audio] Adam to present. Phase 1 - Functional Testing.

[Audio] Adam to present. Phase 2 - User Experience Testing.

Roles and responsibilities. Roles and responsibilities Project Lead Rajeev Tyagi Support contact Lead for project and testing Co-ordinate overall test scheduling, resources and execution. Provide support and assist in trouble shooting and resolving test environment issues Responsible for providing test progress and outcome reporting. Categorise test results Project Support Manager Monica Benivento Support contact person Assist in development of testing plans and test cases and provide support Provide support to the Project Lead Coordinate all phases of the testing period Develop test cases Report and record defects / arrange test results updates Communications Melissa Passe-De Silva Assist project team with communications Phase 1: User testers Content Owners and SMEs​ To test and validate the contents on the Playbook keeping users in mind. Contents relevance, sufficiency, and accuracy Language consistency Links and Navigation Contacts Phase 2: User testers Nominated users in the Business Validate fit for purpose by completing test cases..

User Testing. 11. Categorisation of Feedback from Functionality Testing and User Experience Testing.

12. Next Steps. Sep: Emails / Yammer / IP SharePoint - Include link to the new IP Playbook and an overview of purpose and intent; and encourage feedback Next Steps Sep - Dec: Post Launch follow-up, feedback mechanism, prepare for next versions and on-going maintenance Sep - Dec: Further build this site so that all our key resources are available from IP Deliverer Playbook SharePoint site.

Working with our clients Transport operating model As one Transport team. we're working together for our customers, our communities and our colleagues. To help us put the customer and community needs at the centre, we've created the Client Deliverer Model. It sets out the key roles and responsibilities for how we work together across Transport to deliver customer-facing and projects and is a fundamental part of the Transport operating model. There are four core roles within the Client Deliverer Model: Client. Deliverer. Internal partners and Sponsor. Infrastructure and Place (IP) is a deliverer within the Client Deliverer Model. The Client Deliverer Model depends on strong collaboration and open communication between the client and deliverer. as well as with our enabling divisions and partners. Visit the Client Deliverer Model site to learn more. A trusted partner to our clients We seek to be a trusted delivery partner to clients, working closely with our client divisions, Greater Sydney and Regional and Outer Metropolitan, to develop and deliver a solution that the Client has approved. We provide the technical expertise and work closely with the client to deliver projects on time, to scope. and within the budget provided by the Client. Bringing the Client Deliverer Model to life Collaboration between all parts of Transport is critical to bringing the Client Deliverer Model to life, to ensure we deliver great outcomes for our customers and communities. While all divisions across Transport play a role to enable, support, and regulate the way the Client Deliverer Model is implemented, IP works closely with Greater Sydney and Regional and Outer Metropolitan. as these divisions most often are the "Client" for IP in our projects and programs. More information and support Quick links Client Requitements Template Cl•ent Wvere•r Model SharePoint Site Governance Project Brief Pr#ct Initiatives Contact C bent Interface.

ary Edit Capital Pr*ts Framework" Pr*ct Initiatives.