Notes
- This combines information from different perspectives
- Product Acquisition
- Service Portfolio
- Issue Escalation TBD
Need to explore product and service dependencies, nesting and components
Have Owners defined for Services now, and Organizations for Products, but that is to provoke discussion
Are Keys and Files important and if so how should they be linked in
Product Owner Conceptual Model.jpeg
Some key points in terms of optimal business rules:
- owners
- only one financial owner
- only one business owner
- only one service owner
- they could all be the same person
- this will enable decision making and illustrate clear roles and responsibilities
- contracts and agreements
- one agreement can have many purchase orders
- each purchase order should reference only one agreement
- access and authorizations
- we want to know who has access to use what
- but we do not want this tool to do enforcement
- products and services are being treated as separate entities
- need to figure out what to do about services consuming other services (nested)
Steve has offered to reach out to Nancy Gift on UXD to help us develop some user stories to complement this process.
Upcoming meetings:
October 14, 2010 4-5pm N42-202
- IS&T Software Portfolio with Paul and Allen
- draft processes to map into swim lanes with Scott
- updates on pilots (feedback)
October 21, 2010 1-2pm N42-202
- review draft charter for Release Core
- updates on pilots (feedback)
October 22, 2010 1:30-3pm W92-199
- business process mapping with Scott (swim lane diagrams)
- review user stories if available
October 28, 2010 1-2pm N42-202
- review charter for IS&T Pipeline
- updates on pilots (feedback)
November 2, 2010 3-4:30pm W92-278
- finish conceptual modeling with Scott
November 4, 2010 1-2pm N42-202
- finalize charters
- updates on pilots (feedback)
November 10, 2010 3-4:30pm N42-202
- review conceptual models and business process diagrams with Christine and Barbara
- discuss how this might feed into the IS&T Service Catalog
- define next steps