Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 5
Date
Attendees
Goals
- Retro for the FedX working group
- We will run a mute mapping-based retro to see what's working and what needs improvement
- Areas to reflect on before attending:
- Why do you come to the FedX meetings?
- What benefits do you personally get out of the meetings?
- What aspects of the meeting are working well?
- What should we be doing differently?
- What should the output of these meetings be?
Discussion items
Time | Item | Who | Notes |
---|
5 mins | Mute Mapping explanation | | - Process
- Everyone write ideas down on stickies (the virtual ones!).
- Gather stickies in piles of similar themes (yes, people will move your carefully placed sticky around. It's all cool.).
- Name your piles.
- Vote on your piles.
- Want to learn more?
|
30mins | Mute Mapping retro | Everyone | 5/31 - FedX Mute Mapping |
25mins | Discussion about how the group should work going forward | Everyone |
|
Resourcing & Prioritization
- How do we affect the roadmap?
- How do we get clarity around an idea and getting resources to move forward?
- Can we drive for change ourselves?
- e.g. webpack
- Bias toward action
- The group gathered around webpack and started making the changes
- e.g. bootstrap
- Learner team just started doing it
- We were able to incorporate new technologies through opportunistic projects
- Cons
- increases scope
- learning is difficult and time consuming
- Proving the technology within an IDA is easier
- How do we influence better?
- It's difficult to decide on the front-end guidance within a clear vision of how we render
- Strategies
- test in IDAs and/or small projects, prove the results, share the information
- trainings (either our own or good courses that we find, lunch and learns)
Action items