Versions Compared

Version Old Version 1 New Version Current
Changes made by

Prabhu Kannan

Liz Enright

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Team Vision

Team Culture

Team Details

Liz Enright Yeng Sembrano Manpreet Sidhu Sakshi Chauhan (Unlicensed) amit.sood (Unlicensed) jessica.wood

Defination of Ready

Defination of Done

Summary

Child Pages

The Avengers team was spun up to address ongoing data quality challenges. This team focused on Salesforce architecture, data integrity, and integrations to an extent.

Child pages (Children Display)

Squad Vision

Fast track the reliability of an Alumni and Donor centric quality system to support the facilitation of a best in class experience to drive alumni and donor university wide engagement and pipeline activities

Squad culture & values

  • Just do it

  • Supportive

  • Collaboration

  • One team

  • knowledge management (confluence)

  • Transparency

Squad Details

Profile Picture
User5d364de46e55370bc308d1ac
- Customer success manager, change management

Profile Picture
User557058:9184676d-fff1-4341-9e7f-881d9109c0e0
- SME/Product Owner (Part time)

Profile Picture
User5e6570e241833c0d0b6a0138
- SME/Developer (Part time)

Profile Picture
User5c9315941b780c2c5d7c1c04
- SF Consultant/Developer

Profile Picture
User62a15e29be336c006fe9330b
- SF solution Architect

Profile Picture
User60b44106a5be0a0069b02191
- SME/Product Owner

Profile Picture
User62959e33658d580068883a26
- SME, BA

Profile Picture
User5c57a23f5f41f43200d9a263
- Product Manager

Profile Picture
User5e85344f9e34c00c17e2a668
- SME/Product Owner

Profile Picture
User5ee95371a228c50ab9371d8c
- SME/Product Owner

Profile Picture
User5e703532ab4d3f0c3d065818
- Servent Leader

QA ?

Definition of Ready (DoR) for Sprint

Definition of Done (DoD) for Sprint

  • Requirement is captured in form of user story

  • AC’s are captured, reviewed and agreed

  • Solution or strategy Design for each user story

  • Solution is reviewed and accepted by story owner

  • Story estimation in form of points

  • All the dependencies (including test data for external systems) to implement stories are identified and agreed for resolution during the course of sprint cycle

  • Data dictionary to be defined along with Single CRM (confirm with Yeng)

  • Everyone in team are having common understanding of the story and outcome expected

  • All the necessary access and tools are in place

  • Change management meeting in place

  • All the acceptance criteria written in story are met (Unit testing and functional testing)

  • Implemented stories are tested/reviewed by respective product owners / SME

  • All the outstanding questions related to implementation are resolved

  • Stories & Subtask are marked as “Done”

  • Update the config workbook/Solution Design to keep track of all the configurations done

  • Code review and unit testing completed

  • Showcase completed for all completed stories by end of sprint

  • Hands on training session (minor and medium changes) to be completed for each sprint following sprint Showcase

  • Knowledge document (SF article, video in MS teams) at feature for completed stories

  • Regression testing is must, reach out to Brad Fernandes (Unlicensed)

House rules:

  • Openness

  • Mindful of commitments (eg conflicting schedules)

  • Progress summary in general (sprint review)

  • Daily updates

  • No task should be taken up outside of the Jira backlog

Team cadences:

  • Sprint cycle: 2 weeks Start 29th June (Wednesday to Tuesday cycle)

  • Stand-up: 10:15 to 10:30 AM Daily

  • Refinement: Tuesday 12 to 01 PM Weekly revised to Tuesdays 10:30 to 11:30

  • Sprint review, Showcase: Clubbed with TAP PL

  • Retro: 30 min slot Monday (Yet to be scheduled Prabhu Kannan)

  • Sprint planning: first day of the sprint

Jira Process:

...

  • Blocked Stories/Follow-up required story/task will be flagged with the most recent update/comment.

Sprint Health:

Sprint #

Objective

Timelines

GOAL Status

Planned Vs Achieved (story points)

Sprint 0 - Avengers assemble

Team formation, Define backlog structure, refine stories for Sprint 1

to

Sprint 01 -

Sprint 02

Product Road Map

...