The Ripple Effect- My Project Portfolio

 Ok let's pick back up. I recall I needed to blogsplain a few items to you, as the reader.  1. What is agile? 2. What is a story? 3. What is a requirements matrix? 4. What tools do I use daily? Agile- this is a form of how you manage a project that encourages smart development, in an iterative approach ( just means smaller cycles) with adjustable scope. You work with an assigned team and you build your stories (defining this next) and from there you gather work and tasks and make a commitment to that work only (sometimes there is a spike) within a two to four week period. I have found that two weeks is the sweet spot, four weeks work can get procrastinated and become unfocused. Story/ies- this is a written statement that presents a wish from the business in a relatable standard to the team. I like to use the Story, Scenario, Given, When, Then model. Let me give you two examples:   User Story Scenario Given When Then Priority 1-3 ex. As a customer I want to se...

 This project is not simple by any means. But, then again, most of the project level work that I am assigned is not simple     : )  Currently the organization that I work for is using an on prem contact center solution and they have tasked me to take them from 20 year old software to a new SaaS model this year. Wow, as I write it it sounds so simple... like a single sentence right? Well let's dive into why this is not as simple as a single sentence by me sharing you the current and then me showing you the "to be". To kick things off with a bang how about a visual of business requirements. It is so huge it will not be legible, but it gives context to the size! Also know I do not have all the map bubbles expanded. Incredible.... that I do this work on a daily basis. History Now let's give you some history of this 20 year old software. This was before my time but from talking to the business I have determined that we have been on the same system for a very long tim...