...
What went well | What needs to improve | Actions |
|---|---|---|
no scope creep, careful not to inflate tickets with added features - BS | Design needed dedicated time the previous sprint before the new event invite process - KK | |
communication and collaboration when expectations were uncertain - BS | Tickets were not well defined at start of start of sprint - JK | |
Estimates ended up accurate - JM | Forgot about estimates and logging my time - JK | |
Team helped in reviewing/testing on local, which made me focus more on dev testing - SR | Forgot about logging the time for testing - SR | |
Sprint felt a little crunchy on Wednesday/Thursday morning - JK | ||
Working on the Sidescroller was very seamless (KM) | Still figuring out some of the correct timing on things (ie sidescroller) (KM) | |
Teamwork makes the dreamwork - JK | How do we move from the testing to release stage? -LR | |
Overall progress is very good - LR | Entering time into the Jira board is hard to remember (JM) | |
Gathering assets for the sidescroller was very fast - JM | ticket descriptions…. should have clear spec and testing instructions | |
Did not have too much of a workload - MA | ||
Design time being implemented into our process so that Klaudia does not become a bottle neck like last week (KM) | Still figuring out exactly how to get tasks brainstomed and designed 2 weeks ahead of time (KM) | |
Bray was a superstar with the event invite process - JK | ||
Design items need to be looped back with Klaudia so that she know what did and what didn’t work in development (KM) | Klaudia can join the feature showcase meetings to see the items in action | |
...