Connections to set up

• People and leave systems. Arrange the handoff for personnel changes and availability information with the team that owns those records. Agree how that information affects the weekly capacity baseline used in planning.
• Existing task tools. If another system owns delivery tasks, define which system controls assignment, dates and progress before transferring records. Keep project and package identities consistent.
• Source control and release tools. Agree how relevant delivery evidence reaches the attached files or links used in review. Keep the review subject recognizable when an external reference changes.
• Document storage. Connect the approved document location where the team wants to retain requirements, designs or review evidence. Set access so reviewers can open the intended file.
• Payroll and invoicing. Agree any transfer of time information with the system responsible for payment or billing. Define the included time states, identifiers and correction procedure before enabling a connection.

Name an owner for each connection and agree the source of truth for every field it updates. Rehearse a failed transfer and a repeated message so the team can explain whether the intended record changed. Protect credentials through the customer’s normal access process.

Keep the planning review understandable when systems exchange data. A changed task date affects the planning period; a personnel change can affect personal filters and access. Review the data model and the pilot case before enabling transfers on live work.