...
Versioning Strategy and Accountability
- Chris Cadden and Jesús Rangel - Document Outsystems vs. Non-Outsystems and definitions
- Rebecca Schneider - Review Project Plan continuously and integrate dev feedback earlier in the process
- Kim Roark Loveland - Pre-kickoff release planning with the entire team
- Netal Patel - Define team strategy and expectations for versioning
Documentation and Accountability
- Chris Cadden to review the design standard documents in the weekly dev meeting
- Development team MUST adhere to defined processes
- Chris Cadden to collaborate with Grecia to formalize standard documentation of design
- Team to commit to documenting reusable, successful tools in the moment
- Netal Patel and dev team to prioritize working with OutSystems to research/spin up an internal forge
- Candace for Updating Components - Rosa Illescas and Netal Patel
- Dev team to review Application Feature Inventory - /wiki/spaces/CADKS/pages/4049371146
- Team to Involve QA at the beginning of process
- Selene Gutierrez and QA team to create standard documentation on process and templates/checklist for UAT
- Team to help Rebecca Schneider make Project Plan a core part of the process
...
- Rebecca Schneider to present metrics based on estimation vs. actual during retrospectives moving forward
- Netal Patel and Rebecca Schneider to define metrics to be reviewed
- Netal Patel to investigate Accessibility Training Opportunities between QA, Dev and Accessibility
- QA team to share their testing process
- Team to commit to more active communication and review in retrospectives
Deployments and Accountability
- Rebecca Schneider to review project plans on Mondays to allow for review and feedback of deployment schedule
...