# data[].attributes.body
- focus on one project (e.g. 1 epic per sprint)
- Discuss with Postbank that it is more efficient to focus on 1 topic at a time

# data[].attributes.body
- requires time
- all team members should now each others code and know on what the others are working (in detail, spend more time on this)

# data[].attributes.body
- document in confluence
- use it in all documents / artifacts
- schedule separate meeting on this

# data[].attributes.body
- keep documentation clear for only Android (screens, only Android related spec)
- link to old stuff, make clear when transit to iOS documentation

# data[].attributes.body
- Commit only on things that can be closed in the sprint (incl. testing, design review, bug fixing)
- Say "NO!"
- End of the Week -> Discuss about "Spare time at the end of the sprint"

# data[].attributes.body
1

# data[].attributes.body
2

# data[].attributes.body
1

# data[].attributes.body
1

# data[].attributes.body
1

# data[].attributes.body
+3

# data[].attributes.body
2

# data[].attributes.body
1

# data[].attributes.body
1

# data[].attributes.body
1

# data[].attributes.body
2

# data[].attributes.body
working on smaller pieces

# data[].attributes.body
= single feature release focus
= one epic per sprint and whole technical team on one epic

# data[].attributes.body
Define project specific DSL

# data[].attributes.body
Great team communication in Android team

# data[].attributes.body
Too many unfinished things (Multibanking, Syncbox, mPay)

# data[].attributes.body
Android UI tests are behind iOS by huge margin. We should work again on it.

# data[].attributes.body
- Communication issues due to not single language used describing app specific components and mechanisms.

# data[].attributes.body
- Issues based on lacking discipline in Branching model.

# data[].attributes.body
- Given workload in time (number of tracks), rushed QA activities with lesser quality of test documentation, especially in context of regression scopes (which for mPay are basically not existing).

# data[].attributes.body
- Documentation quality drop, at least based on Multibanking track, already done by iOS team.

# data[].attributes.body
+ Team communication
+ Being patient

# data[].attributes.body
"process" discussions -> release trains (defined time, variable scope)

less topics on preparation (concept & design)

# data[].attributes.body
- switching between "teams" (syncbox <--> regression)

# data[].attributes.body
open scope

# data[].attributes.body
- Team reduction

# data[].attributes.body
-team reduction
-no further realization redesign
-too many prepared designs

# data[].attributes.body
Team reduction

huge Mpay problems

too many projects in parallel

The neverending sprint

# data[].attributes.body
team reduction

# data[].attributes.body
- the big merge
- "Hamster" sprints :)
- team reduction...
- a bit foggy situation regarding process
- too many epic branches --> too many bugs
- team splits and then knowledge transfer  is very difficult
- iOS stories were not always adapted correctly for android e.g. Release Tour

# data[].attributes.body
prod mpay enrolment

# data[].attributes.body
- Team Reduction
- Regression Wave (big topics)
- Non sorted/priotized board with parallel projects
- cannot add too much since I only joined partially/later