Invited Attendees: Core Team (9 members)
Todd Hoffman
Tina DuBois
Stan Koprowski
Jeff Perkinson
Ashley Prince
- Kathy Cobb
- Carol Gretz
- Jon Weisz
- Antoine Smith
Happenings since Last Status Meeting
- Stan spent the past weeks meeting with additional stakeholders that were available, sharing project goals, reviewing existing artifacts, and describing his role and processes we are using to identify requirements and scope.
- Kathy Cobb, Ashley Prince and Stan met multiple times to continue developing the business events and updating the the context diagram. Carol and others have been filling in gaps for various systems through the missing information flows message posted to the Ask and Discuss board.
- Kathy Cobb, Ashley Prince and Stan ranked the business events on several categories including, business impact, pain threshold, frequency/likelihood and removal of opportunity ID from Orion.
- The team continued to define the business events by identifying the inputs and outputs for each of the events using the existing information flows.
- Tina and Antoine have made some updates to Salesforce to accomodate the changes to SLG.
- The team has begun to define the event response models for each of the business events focusing on the top prioritites.
- The team has begun to create the data dictionaries and the mini specifications (scenarios) for each business event.
- Stan has created a weighted mean score for each of the business events identifying the top 7 events as priority.
Upcoming Milestones
8/18/2017: Business events defined*
8/18/2017: First pass cost estimates available*
8/25/2017: Business Use Cases (BUCs) initiated*
8/25/2017: Data dictionary initiated*
*on schedule as each of these activities has begun
Open Issues
How to gather requirements for Japan, Asia Pacific and rest of world?
Upcoming Event
Work session—business events
Work session--BUC, scenario and user story sessions
Briefly, the business events shows us which information flows are needed as inputs and outputs and how they are related to one another. The efforts here will allow us to begin to understand how we can partition the work and provide better cost estimates.
The responses to the business events will lead us to specific business use cases or BUCs. The effort and timing around the BUCs will further depend on the open issues with other parts of the world as the team has focused primarily on US information flows.
New Issues/Action Items
Team discussion—
Stan will continue to introduce appropriate models that will be used for predominantly communicating the scope, prioritizing the work using business use cases and product use cases. Additional models will be utilized as necessary and may include, data and activity flow diagrams, data dictionaries, CRUD checks and others.
@iluvsamz: Schedule meeting with SAS/IT and systems owners to get everyone on the same page
Stakeholder identification—
Additional stakeholders have been identified that might be impacted by the project. Stan will continue reaching out to them to gather additional details as their schedules allow. Stan has asked members of SAS IT to begin regular participation in the weekly team meetings.
Project related--
Reminder to everyone to continue to add documents and post questions to the pertinent board as needed.
