seat58F
outsourcing relationships: international, inter-economic, interpersonal
September 4, 2010 ~ 10:42:00 AM * -07:00ST
be reflective
Post # 575 by
admin on June 23rd, 2009 ~ 11:17:25 AM
Posted as app services, retrospective |
No Comments »
once the project metrics are recorded and client satisfaction details are collected, evaluate project success based on the service provider business objectives
go live (and cleanup)
Post # 572 by
admin on June 22nd, 2009 ~ 11:03:57 AM
Posted as app services, code release |
No Comments »
- Release Note published
- source code repository updated
- KT per the project plan
- production gate checklist completed per the project plan
- deployment quality control checklist
- client acknowledgement
get the user involved
Post # 569 by
admin on June 21st, 2009 ~ 10:59:01 AM
Posted as app services, testing |
No Comments »
- user acceptance test and scenarios are pre-defined
- scenarios are reviewed (and obtained from a library) and approved by the client
- test findings are logged and tracked to closure
- system testing executed per the project plan
- test findings are evaluated by stakeholders
pound the code
Post # 563 by
admin on June 20th, 2009 ~ 09:34:38 AM
Posted as app services, construction |
No Comments »
Use one, and only one, code repository. Code should not be spread across multiple workstations.
- coding standards are in use
- Unit test cases are available (hopfully re-used, not re-invented)
- test case findings are logged and tracked to closure
- unit testing is occuring as planned
- unit test defects are tracked to closure
backing out of the garage and into the street
Post # 566 by
admin on June 19th, 2009 ~ 10:50:22 AM
Posted as app services, testing |
No Comments »
- system test plan and scenarios are pre-defined
- scenarios are reviewed (and obtained from a library) and approved by the client
- test findings are logged and tracked to closure
- system testing executed per the project plan
- test findings are evaluated by stakeholders
solution design
Post # 560 by
admin on June 18th, 2009 ~ 09:12:59 AM
Posted as app services, design |
No Comments »
The System Requirement Specification for an app maintenance activity is the link to the architectural realities of the infrastructure. Verify that it has been reviewed and approved. Review findings should be resolved prior to approval.
pliable, not frozen
Post # 555 by
admin on June 17th, 2009 ~ 09:03:09 AM
Posted as app services, project monitoring |
No Comments »
the project plan needs to be continuously updated and reviewed on a weekly basis. look for:
- re-planning triggers
- client sign-off on revised estimates.
- tracking sheet (Issues Log) maintenance and communication
- Defect Logging is occurring (”major” and “fatal” defects are addressed before moving to the next phase)
- Risk Analysis and Log is updated
kickoff
Post # 549 by
admin on June 16th, 2009 ~ 08:19:52 AM
Posted as app services, project planning |
No Comments »
stuff that should be on the table:
- complexity evaluation
- ballpark effort estimate approved
- High Level Solution (architecture) and schedule
- client business unit and IT sign-offs obtained
- project workspace provisioned
- SOW updates as required
- Security Plan updates
- Operations training and SOP updates
- SLO updates
everybody pointing in the same direction?
Post # 546 by
admin on June 15th, 2009 ~ 08:13:43 AM
Posted as app services, requirements |
No Comments »
check the Business Requirement to verify that the Functional Requirements and the UAT have been satisfied.
verify that client business unit and IT approvals have been obtained.
verify that the Quality Gate Checklist is complete.
additionally insured
Post # 540 by
admin on June 5th, 2009 ~ 10:41:05 AM
Posted as contract mgmt |
No Comments »
if flow-downs exist, the Business Office Manager already has contractual insurance obilgations under control. any issues regarding certificates should be registered in the issue log.
