Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au
Skip to end of banner
Go to start of banner

Team Avengers - Team Space (Quote: Avengers, assemble!)

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 13 Next »

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

- Customer success manager, change management

- SME/Product Owner (Part time)

- SME/Developer (Part time)

- SF Consultant/Developer

- SF solution Architect

- SME/Product Owner

- SME, BA

- Product Manager

- SME/Product Owner

- SME/Product Owner

QA ?

Defination of Ready (DoR) for Sprint

Defination 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

https://sydneyuni.atlassian.net/jira/software/projects/DTF/boards/1066/roadmap
  • No labels