Concourse & Jira DC Portal

Thanks for the chat earlier. I have the following observations

Background about SMBC and impact(1) Earlier in the year we completed a phase to create a solution blueprint (in effect P1 stage), therefore this project P1 onwards from however in Concourse there is no way to simply way to exclude stages / sub stages(2) We decided to write our Engagement Letter and workorders following the client delivery methodology (not PDM), therefore the PDM stages and sub stages generated by Concourse all need changing

Challenges with the standard delivery plan(3) The generated delivery plan is very granular with no simple way to select the granularity you want, We need to have a option to specify the level that we want the plan to be generated, i,e. At the level immediately under Activity (client deliverable, internal deliverable, event). Currently you have to use Rovo to delete these(4) Allocation to tasks to workstreamsIn Concourse you can create workstreams, but this is ignored by the plan and you are left with a manual task of updating it using Rovo (even then it seems like we should actually be creating JIRA Teams to manage the people in JIRA)(5) Allocation of tasks to a timelineThe delivery plan is imported with no start dates or due dates and it a manual task to update.

Operationalisation of JIRAWe cannot find any materials that explain how to do (4) and (5) We cannot find any training guides for RAID

Gaps in JIRAThe Metlife project shows what is possible in JIRA - perhaps the north star;Critical PMO items like

• Springboard for your PMO

• Status Reporting

• Onboarding/Offboarding

• Roster

• Deliverables Management Workflow and approval

Should be available rather than having to copy from Metlife.

Mandatory tasks are too granular: Some PDM mandatory tasks are listed as separate steps, but they are actually carried out within a single document (e.g. create, review, update and baseline)- attached,

RAID is another example attached

Deliverables vs instructions: SMBC's feedback is that we need to distinguish meaningful deliverables from procedural instructions as it creates artificial complexity (5000 items e.tc) . This is the main reason the team has found the plan difficult to operationalise.

AHA Feedback.png

RAID.png

Attachments Open full size