Meeting notes: Brainstorming process issues 2023 Jan 05
by germaine.oliver@ · 16 things on Twos
- Invited: Brian and Germaine
- Discussion:
- Viewpoints:
- Brian: wasn't sure what the depth needed was, or what the final product needed to look like
- Germaine: seemed like it was being worked, then Brian disappeared
- What became clear: Brian was floundering for much of the time, was trying to guess what some of the definitions were, and what the output or deliverable would be. "Retention and engagement data" is too high level to be actionable, and the deliverable was poorly defined.
- Germaine's thoughts: Using the Agile construct more effectively would have avoided this charlie fox. Therefore, we need to use agile methodology better. Also, bidirectional communication needs to happen, and Brian needs to raise the question marks rather than trying to solve them in his brain. For example, Brian applying brain cells to "how do I present the data" is a waste of effort.
- User story must be more mature: User story, acceptance criteria, definition of done. all typically need to be completed.
- In addition, I have found providing context is super helpful for the devs to ask smart questions... if they know WHY something is being done, they can recognize when there's a gap.
- Dev must understand context and intent of user story.
- Standups/Slack for clarification.
- If dev can't deliver in a sprint, the user story needs to be made into an epic and decomposed. That is a conversation between PO and dev.
- Things to discuss at tomorrow's planning meeting:
- will using the Agile methodology more completely address known process issues better?
- How do we convey timelines/suspenses/urgency more effectively?
- How do we discuss quality vs speed?