• Timebox: 2-4hrs/2 weeks iteration
• Purpose: The team defines and commits to what will be built in the next Iteration
• Attendees: PO, SM, Agile Team, and invited stakeholders
• Facilitator: SM or PO
• Preparation:
  • Team capacity and velocity are established
  • Team PI Objectives and Features
  • Candidate's stories for the iteration are READY and prioritized

1. Establish the Team’s capacity and velocity
2. Revisit all the READY stories/enablers for the Iteration
3. Discuss how to complete each story/enabler
4. Load stories into the Iteration until capacity is reached
5. The team commits to the iteration goals

•  Invited Development stakeholders are present
•  Team capacity and velocity/load are revisited if necessary
•  DoR and DoD for the sprint are revisited if necessary
•  Each story/enabler is revisited (description, AC, size, ...) and passes the DoR
•  Team capacity allocation is established (load allocated for maintenance, refactors, tech debt, or any relevant work item type)
•  Sub-tasks are created to highlight how to complete a story/enabler when necessary
•  Stories & enablers planned for the upcoming Iteration respect the team's velocity
•  Iteration's goals are defined
•  The team commits to achieving iteration goals
•  Iteration is started at the end of the meeting

Notes:

• The team closed the sprint today (10/31) since it’s the last day and planning started the same day.
• stakeholder was not present 
• 3 stories carried over for the next sprint. Out of 38 stories committed in this sprint 1.
• HCD uses story points per day to calculate capacity. Since HCD is planning for the entire month, it is difficult to plan work ahead without estimating the scope of work vs. how many numbers of days takes the team to complete the work. The team estimated 22 story points for the entire month of sprint planning.
• During the conversation, the PO is going over capacity and planning, but the team did not look into their backlog to plan priorities. 
• Some new team members have different opinions on sizing since they are new to the team. (Creator Facilitator Story) 
• Some stories committed to this new sprint are being pushed to the next sprint. the team is not looking at their backlog during planning, several stories did not look into Acceptance criteria. 
• PO provides solutions, making it harder to guide the team on the "how" and allowing the team to think about solutions (value desired) on the who, when, how, and why.
• Howard seemed unclear on the story assigned to him on (coms comms and marketing) opportunity to better refined refine and look into DoR/ DoD to ensure the intent of the story is understood/ dependencies addressed prior to committing to the work.
• Unknowns on iQIES effort and work since HCD plans work for an entire month. Opportunity to collaborate with LACE/CMS on expectations on the scope of work and stakeholder
• A team working agreement is being sent to Rob, eventually, the team should be doing it as an activity all at once coming up with specific agreements as a team and reviewing them.
• HCD did an amazing job with its Halloween theme, each sprint has a theme making it fun for the team. 
• The team uses a confident vote at the beginning to ensure the Sprint Commitments can be achieved.