MVPs for the next TeamDynamix modules announced
This article was originally published in the September 9, 2021 IT Weekly.
Project teams for the next modules of the IT service management enhancement project have defined their minimum viable products (MVPs), with target completion dates as early as this Thanksgiving. An MVP is defined as the launch of a foundational product that can be built quickly, provides functionality, adds immediate value, and can be enhanced. The overall strategy is to launch MVPs as soon as possible and then work iteratively on enhancements. This represents a shift to a more agile mindset for the project.
The next modules require the definition of new business processes in addition to launching the new tool. The MVP approach allows teams time to create well-defined user stories, understand the tool鈥檚 capabilities, develop processes and a plan for operating and sustaining after launch. Each team is led by a subproject lead and advised by a member of the project鈥檚 steering committee. The project teams have been meeting with other TDX customers in higher education to learn about their internal processes and implementation experiences. Details on each specific module are described below:
Asset management
The asset management team, led by Ian Isham, has identified two applications, Titanium and Transact Cloud POS (formerly Sequoia), as the scope of the MVP. These two applications have related assets and configuration items (CIs) that touch most technical resource groups, so that each team has an opportunity to understand the platform and develop their own processes.
The team has also worked to define assets and CIs that will be included in the tool. An asset is anything with financial value over $100 that contributes to the delivery of an IT product or service. A CI is any component of a service that needs to be managed to deliver an IT service, such as virtual machines, applications, and integrations.
Problem management
The problem management team, led by Dave Belville, began by developing a process workflow, including defining problems and major incidents, thresholds used to identify problems, and who is responsible for that work. The problem management MVP will include one form with a 鈥減roblem鈥 ticket type to track identified problems, with a target launch date of mid-November.
Service catalog and knowledge management
This team includes work on two modules, both led by Cody Sigmon. The team is aiming to migrate the into the Technology Help Center and link ticket forms to our most popular service offerings by Thanksgiving. Knowledge management, which involves reviewing, migrating, and formatting all existing help content for end users from the OIT website, is slated for February 2022. The knowledge management work is aligned but separate from the larger project to analyze and standardize knowledge management practices for OIT.
The implementation contract with TeamDynamix goes through April 2022, so our deadlines are largely self-imposed and allow us to retain vendor support through launch and the first months of operationalization. If you have questions, please ask them in the .