UCX Platform Development Stakeholder Communication Flow

Get Started. It's Free
or sign up with your email address
Rocket clouds
UCX Platform Development Stakeholder Communication Flow by Mind Map: UCX Platform Development Stakeholder Communication Flow

1. PRODUCT MANAGER/PRODUCT OWNER (RYAN)

1.1. Discussess/shares via email and call High-level business requirements/features planned on the roadmap for each year (USING A DEDICATED TEMPLATE). KEEP THE FOLLOWING STAKEHOLDERS IN EMAIL

1.1.1. CEO, CTO, LEAD ARCHITECT, SOFTWARE DEVELOPER MANAGER, PROGRAM MANAGER & CHIEF OF OPERATIONS (SALES)

1.2. Discusses/Shares via email when a new Partner, new category/sub-category of a Product, pricing options, and other important product attributes every time when they are added (USING A DEDICATED TEMPLATE). KEEP THE FOLLOWING STAKEHOLDERS IN EMAIL

1.2.1. CHIEF OF OPERATIONS (SALES), SOFTWARE DEVELOPER MANAGER, PROGRAM MANAGER, LEAD ARCHITECT, PROGRAM MANAGER & PMs.

1.3. Consults/discusses new technology strategies/market needs/partner requests/new opportunities WITH

1.3.1. CEO, CTO, LEAD ARCHITECT & SOFTWARE DEVELOPER MANAGER

1.4. Sets priorities of features for each release backlog (USING A DEDICATED TEMPLATE). KEEP THE FOLLOWING STAKEHOLDERS IN EMAIL

1.4.1. SOFTWARE DEVELOPER MANAGER/PROGRAM MANAGER/PMs

1.5. Requests changes/improvements to features during UAT week of the Release which are to be included in the next Release Backlog VIA EMAIL (USING A DEDICATED TEMPLATE)

1.5.1. SOFTWARE DEVELOPER MANAGER/PROGRAM MANAGER/PMs/QAs

1.6. Directs/comments directly with UX/UI Designer on the Relevant Task. TAG/COMMENT/CC IN EMAIL

1.6.1. RELEVANT PM, QA

2. CTO, LEAD ARCHITECT & SOFTWARE DEVELOPER MANAGER

2.1. Communicate decisions on technology strategies/integrations etc UPON DISCUSSION WITH PRODUCT MANAGER VIA EMAIL/MEETINGS WITH

2.1.1. CHIEF OF OPERATIONS (SALES), PROGRAM MANAGER, PMs, R&D, DEVOPS, TEAM LEADS

3. SOFTWARE DEVELOPER MANAGER

3.1. Communicates release plans as changes occur in advance VIA EMAIL (CONFLUENCE PAGE)

3.1.1. CTO/LEAD ARCHITECT/DEVOPS, PROGRAM MANAGER/PMs, QAs

3.2. Communicates resource availability from pillar to pillar or Client Based projects as things change VIA EMAIL (ATTACHING A DEDICATED RESOURCE AVAILABILITY SHEET TEMPLATE)

3.2.1. CEO/CTO/LEAD ARCHITECT/Program Manager/PMs

3.3. Takes Action Notes on Technical Meetings and shares with relevant stakeholders depending on the the subject area where relevant PMs can assign tasks to dedicated individuals.

3.3.1. CTO/LEAD ARCHITECT/PROGRAM MANAGER/PMs

4. PROGRAM MANAGER

4.1. Prepares Multiple Project Reporting sheet on UCX Paltform team & new opportunites. Share VIA EMAIL (USING THE DEDICATED TEMPLATE)

4.1.1. US CEO/KS CEO/PRODUCT MANAGER/CTO/LEAD ARCHITECT/SOFTWARE DEVELOPER MANAGER AND/OR PMs

4.2. Updates UCX RoadMap Plan page on Confluence as requirements change. SHARE VIA EMAIL (USING THE DEDICATED TEMPLATE OR THE CONFLUENCE PAGE)

4.2.1. PRODUCT MANAGER/OWNER/SOFTWARE DEVELOPER MANAGER/LEAD ARCHITECT/PMs

4.3. Updates Jira Epics in accordance with the upated version of the UCX RoadMap dedicated sheet. Inform VIA EMAIL

4.3.1. PRODUCT MANAGER/OWNER/SOFTWARE DEVELOPER MANAGER/LEAD ARCHITECT/PMs

4.4. Drafts Company Processes & Best Practices related to the the development of the Platform and shares VIA EMAIL (Attaching a link to the confluence Page if applicable)

4.4.1. CEO/PRODUCT MANAGER/OWNER/SOFTWARE DEVELOPER MANAGER/LEAD ARCHITECT/PMs

5. PROJECT MANAGERS

5.1. Create Sprint Backlog Features according to the priorities of the Epics for a Release. INFORMS VIA EMAIL/SHARES CONFLUENCE LINK WITH A NOTE WITH

5.1.1. PRODUCT MANGER/LEAD ARCHITECT/SOFTWARE DEVELOPER MANAGER/PROGRAM MANAGER & PMs

5.2. Share Sprint reports

5.2.1. PRODUCT MANGER/LEAD ARCHITECT/SOFTWARE DEVELOPER MANAGER/PROGRAM MANAGER & PMs

5.3. Keep Sprint & Release retrospectives with key stakeholders

5.3.1. PRODUCT MANGER/LEAD ARCHITECT/SOFTWARE DEVELOPER MANAGER/PROGRAM MANAGER & TEAM MEMBERS

5.4. Informs in advance when code freeze/all branches have been merged or taken place for a release in order for Release Preparation to be effective. INFORM VIA EMAIL

5.4.1. PRODUCT MANAGER/LEAD ARCHITECT/SOFTWARE DEVELOPER MANAGER/PROGRAM MANAGER & LEAD DEVOPS.

5.5. Share Release Notes accordingly. INFORM VIA EMAIL ATTACHING A CONFLUENCE LINK PAGE.

5.5.1. CEO/SALES/PRODUCT MANAGER/CTO/LEAD ARCHITECT/SOFTWARE DEVELOPER MANAGER/PROGRAM MANAGER & LEAD DEVOPS.

5.6. Communicate issues/risks in advance as they are identified for each Sprint that may impact the target date of a release. INFORM VIA EMAIL ATTACHING A CONFLUENCE LINK TO ISSUES/RISKS PAGE

5.6.1. CEO/SALES/PRODUCT MANAGER/CTO/LEAD ARCHITECT/SOFTWARE DEVELOPER MANAGER/PROGRAM MANAGER & LEAD DEVOPS.

5.7. Consult with Lead Architect when each Pillar can merge into a Devevelopment Environment during internal pre-releases. Communicate via Telegram or Google Hangouts for internal coordination of Activities.

5.7.1. LEAD ARCHITECT/SOFTWARE DEVELOPER MANAGER/PROGRAM MANAGER

6. LEAD DEVOPS

6.1. Prepares the release together with DevOps from each Pillar, fixes any bugs and INFORMS VIA EMAIL KEY STAKEHOLDERS WHEN RELEASE HAS TAKEN PLACE SUCCESSFULLY

6.1.1. PRODUCT MANAGER/LEAD ARCHITECT/SOFTWARE DEVELOPER MANAGER/PROGRAM MANAGER/PMs

6.2. Document all deployment release with specifics needed to the designated Confluence page. INFORM VIA EMAIL (ATTACH CONFLUENCE PAGE)

6.2.1. LEAD ARCHITECT/SOFTWARE DEVELOPER MANAGER/PMs

7. CHIEF OF OPERATIONS (JETA

7.1. Shares Sales requirements that drive business value and which limit the sales progress.

7.1.1. PRODUCT OWNER/CTO/SOFT.DEVELOPER MNG/PROGRAM MNG

8. ADMINISTRATION/HR

8.1. Onboards new staff and informs VIA EMAIL (Attaching relevant forms that fall under the onboarding process)

8.1.1. Software developer manager, PMs, Lead DevOps, cc: CEO/Product Manager-Owner