Managing Strategic Planning with Project Portfolio Management, Agile Development 2.0, and SAFe

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Managing Strategic Planning with Project Portfolio Management, Agile Development 2.0, and SAFe

    This guide provides essential guidelines for integrating Strategic Planning with Project Portfolio Management (PPM), Agile Development 2.0, and SAFe. It emphasizes the importance of maintaining data consistency during the interfacing of records and outlines specific actions to prevent data issues.

    Show full answer Show less

    Key Features

    • Filter Conditions: Avoid changing filter conditions of table maps after records are interfaced to prevent data inconsistency. If a change is necessary, manually update the relevant attributes on the interfaced records.
    • Field and Choice Maps: Ensure proper configuration of field maps and choice maps when creating a table map.
    • Execution URL Management: Use the Converted to field on the planning item form to track original records. Ensure the Lookup field and Lookup column values are correctly set when referencing different tables.
    • Data Synchronization Checks: If synchronization fails, verify the integration error logs, filter conditions, and the active status of integration and table maps.
    • Primary Goal Field: A new Primary goal field in project, demand, and epic table maps enhances integration between alignment and execution tables.
    • Table Map Creation: Table maps can be created for any execution table but specific rules apply if not based on delivered tables.

    Key Outcomes

    By following these guidelines, ServiceNow customers can ensure effective integration of strategic planning processes, maintain data integrity, and streamline project and demand management. This leads to improved alignment between planning and execution, enabling better decision-making and project outcomes.

    Ensure that Strategic Planning is integrated properly with PPM, Agile Development 2.0, and SAFe with these guidelines.

    • Do not change the filter condition of a table map after the records are interfaced. The already interfaced records might not match with the new filter condition and any change in the filter condition can result in data inconsistency. If you need to change the filter condition, ensure that the relevant attributes on the interfaced records are updated manually to avoid data inconsistency issues.
    • Whenever a table map is created, ensure that the relevant field maps and choice maps are also configured.
    • When an import job for a table map is running (processing), do not modify the table map or its field maps.
    • Using the Converted to field on the planning item form, you can identify the original record from which it was converted.
    • Ensure that the Lookup field and Lookup column values are added whenever the execution and alignment tables are referencing two different tables, while creating a field map for field type of reference or glide list.
    • If there is a data synchronization failure, check if:
      • The Integration error logs related list within that Alignment integration record.
      • The Alignment table filter (for import) and Execution table filter (for export) conditions are met.
      • The Active flag in both the alignment integration and the table map is checked.
      • The appropriate fields and choices are configured for each table map.
    • If you want to view the Execution URL field, configure the alignment planning item record to view it.
    • If the Execution URL field in your synced planning item(s) is blank, navigate to Strategic Planning > Integrations and click Fix execution URL(s) for planning items. This action creates and updates the execution URL field.
    • A Primary goal field is introduced to the projects, demands, and epics table maps to support the integration of the Goal field between alignment and execution tables.
    • When you are trying to import or export a project, ensure that the demands (that are a part of that project) are synced.
    • You can create a table map for any execution table. If a table map is not created from one of the delivered tables (pm_portfolio, rm_epic, dmn_demand, pm_project) or does not extend from them, you are required to create a business rule to support the interfacing of the table map records. For more information on creating a business rule, see Create a business rule to apply a custom table map configuration.