Kicked Off and more.... Sorry about the delay : )

 Well do I have some updates for you. The contract was signed and within a whirlwind got to interview our proposed consulting team and then it was like bam.... we are here.

We are into discovery design (approx. 2 weeks) of intense brain drilling questions about business logic, rules, flows, architecture, workbooks etc. It is going faster than a bullet. The team is keeping up as best that they can, but all of this change is pressing in at this point in time. As the PM I am focusing on really over communicating, sharing info, encouraging cross team collaboration and answering questions. 

Plot of start:

Session 1 (2 hrs) all about inbound. Following the SOW of promising (3) call flows painfully going through our current call flows and asking does this still make sense. Many decisions in these flows were made pre my time (15+ years ago). We tackled our main &*** DNIS and selected two other call flows that made logical sense to have built. Now I am working on identifying all the other 20+ call flows to ask are we keeping or donating to the burn pile.

Session 2  (2 hrs) all about wrapping the other two call flows and breaking ice on BYOC (bring your carrier to our software). It was a bit like a ghost town with the engineers lol. We will do a workbook to talk about SBC (session border controllers) and Protocols and such and go from there. I did find out were are not changing carriers in the middle of this big change which gave me some relief.

Session 3 (1.5 hours) Telephony and Integrations. There are a tangle of other applications that we as a team have to make sure all play nice for cut over. We got on prem apps, databases, cloud databases, dashboards, galore to fit in.

Session 4 (2 hours) now we enter digital.... email, chat, sms. Whatsapp, etc. Approaching as a test so the business can slowly learn the new. Got a good use case for Tech Support and some ticketing type needs. So. ROI on the brain for sure for this team and the business 24/7.

More to come...to give purview our burn down went up...how is this possible LOL- gotta tell the team quit putting stories to active post Sprint start haha. They are learning... ya know? Ignore day 1- that is a JIRA bug, so it shows day two of when we entered all stories. I may change the start date to make it look normal... still debating. Anywho we wrap Friday and the team has clearly over estimated. Hey this stuff is not for judgement. That is my main point- it is to learn...period. So future employer just know that tools are tools but people matter more. When you take a team that is not familiar with such stuff as SCRUM and Burndowns/ estimates you do not want to say ok so we failed. ANY story this team closes is a WIN in my books.