Last active
April 26, 2017 09:28
-
-
Save saurabh2590/7c4ed18f6fdf8a8e592626a8a5854941 to your computer and use it in GitHub Desktop.
Dev Team Retro
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Good | |
| - good introduction about the project. | |
| - Clear specifications on the priorities of the tasks | |
| - On boarding process seems to be more robust. | |
| - Pair programming sessions with colleagus. | |
| - Opennes to innovation. | |
| Bad | |
| - Focus on finishing the stories & ambiguity, lagging behind MVP. | |
| - Less focus on UX/UI | |
| - Less comfortable with esitmations due to no background knowledge. | |
| Risk | |
| - Planning on the overall project. | |
| - UX/UI implementation | |
| - Strucutre and responsibilties. | |
| Ideas? | |
| - More structure to show and share. | |
| - Identifying owners for topic and pre-paring the schedule for on-boarding might help. | |
| - Informing in Advance on the tech meetings to help participants prepare better. | |
| - From offshore, advanced notice on estimation help them to prepare better. | |
| - Involve UX/UI more into dev process and have quick prototyping support for UX/UI ideas. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment