P2P

60 P E E R T O P E E R : I L T A ' S Q U A R T E R L Y M A G A Z I N E | S U M M E R 2 0 2 2 Map Out Future State Once you have analyzed the current state, map out your future state. How do you want each project artifact to look to meet the needs of the majority of your projects? Don't stress! Because we are continuously improving ourselves and our processes, these templates can be updated to meet the evolving needs of your team and project. Here are some questions to get you started: Lists • What lists do you need (e.g., RAID logs, Change logs, Defect tracker, Lessons Learned)? • What standard columns should be incorporated? Don't worry; it doesn't have to be perfect from the start. The Project Manager or the team can add or update the columns based on the project need. However, it helps to identify the "must have" fields across all projects. • Which columns will you want to report on? These columns should utilize drop-downs (i.e., pick lists) to maintain consistency. What should the options be? Be mindful of the end result and the reporting that you may need to present to the team and executives. OneNote • Do you want a shared OneNote notebook (always Yes!)? We highly recommend this tool for project documentation like meeting notes and storing key emails everyone needs to refer to. • What sections do you want to have in your default notebook (e.g., Meeting Notes, Correspondence, Research, and Data Dictionary)? We used our project methodology as a guide to structure and standardize our OneNote sections. As a result of this exercise, we added new templates like a Roll-out Communication Plan to track the different F R O M T H E T E C H S O L U T I O N S C C T

• Cover