Getting to green
@Karen Israel
Major takeaways
Documentation
Preserving the go live checklist
Defining roles, responsibilities,
Having the testers defined early w/ necessary access
Blocking time for testing sessions was helpful
How was team able to get to green?
Teamwork: present, accountable, communicative
Dedicated testing sessions and dashboards
Hard deadline
Visibility and stakeholder support
As best as possible, lay out target schedule; creates urgency where needed
Forcing function to document test cases
Size of project team?
Core team: BSA, QA, PM, Tech leads were core team (relatively small)
Vendor: just a few from the vendor side (relatively small)
Impact: touched every dept and user on campus and health, students and employees (very large)
Informing sys admin groups early, getting list of critical sites, setting up office hours and testing sessions
~50 responses to critical site list
Share experiences on working with contractors and adding contractors
@Mindy Peng
Use case:
Sometimes we also have trust issues, even when there are not vendor quality issues
Best practices
Important to manage expectations that there will be issues and bugs
Important to set expectations that projects needs to be a partnership (not concierge) and behave as colleagues
Stakeholder with the vendor to do formal reviews on issues, risks, billing, any team dynamic concerns
Create smaller SOWs at first, to vet the vendor
Relationship is key with the vendor, like any relationship, to maximize value (output and quality) from the vendor
Variance and opportunity
Share wins and cross functional project impacts and challenges
all
X functional
Wins
Challenges
Putting the tech in technical PM
Technical Concepts
AI
Closing projects! Should be Live
Loading...
Closing projects! Should be Done
Loading...