Omnisharp & SISU Partnership Improvement Meeting 6/11/24
How should OS communicate the right level of urgency?
Adam can’t stop asking “How long will this take/cost?” its his job to balance the budget for our projects
It would be helpful for devs to know what kind of pressure OS is under to deliver X feature
Sometimes OS just needs a rough order of magnitude for things, but PO should be responsible for estimates and the repercussions of them
We’re all doing things that have never been done before. Sometimes, OS realizes that they need to re-prioritize their initiatives based on feedback from various parties. SISU devs also get decisions without context
“We can create a roadmap, IF the dev team is malleable to change when initiatives do”
Sometimes SISU devs are forced to cur corners, when OS didn’t know that they were cutting corners
OS bends over backwards for their customers, it would be in our best interest to adopt the same mentality and practice
Action Items
remind C-suite why it is that we even are working on something
Create SISU escalation and after-hour support numbers in Sprint review
Create a list of SISU perceived priorities for support (Tier 2, After Hours, Manufacturing, Purchasing, Bring-up)
Funnel estimates through the PO
plan for a “If a feature or deliverable takes less than X amount of time, just do it” policy with Adam
Want to print your doc? This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
