# data[].attributes.body
Relearning
Task Switching
Defects

# data[].attributes.body
- Relearning
- Defects

# data[].attributes.body
1- Password ui.
2- favourites module
3- relearning, not documented reqs
4- none
5- blocked by, net rate availability, system outage, slow soap
6- yup
7- finding late bugs in favourite module, after merging it to rc.

# data[].attributes.body
Partially work done
Delays
Defects

# data[].attributes.body
1) Partially Done Work
7) Defects

# data[].attributes.body
2 3 4 5

# data[].attributes.body
Partially Done : Architecture team interrupted?
extra features : a text for secure passwords would have been enough?
Relearning : spreading knowledge about common solutions is still needed
Handoffs : Handoff from Dev to QA needs to improve (trying to give them hints)
Delays : Backend! Password UI back and forth.
Defects : late detection of favorites problems? did we have these tests in the full-test?

# data[].attributes.body
Relearning, defects,delays

# data[].attributes.body
5 7

# data[].attributes.body
relearning from android team from java code
task switching between coding and req clarifications
defects from legacy - too late in the process
delays due to coordination and clarifications
user facing refactoring
delayed by backend, system outages
unfinished tickets
defects in number
relearning the code
lack of information in the tickets from one team to other
better planning for focus
extra features in terms of complicated UI features
misunderstanding of the features
delays because of unavailability

# data[].attributes.body
Defects in number
Defects identified late in the process

# data[].attributes.body
Integration branch for refactoring efforts/testing.
Disconnect testing from release
Start from mocking and prototyping for features which are dependent on outside factors.

# data[].attributes.body
Relearning the code
Relearning from teams

# data[].attributes.body
-@Kiran Need communication from Android team for any clarifications or changes done in the epic/tickets.
= @Kiran SOAP updates communication needs to be also shared between Android and iOS
- @Michi clear in communication of feature descriptions to avoid misunderstandings

# data[].attributes.body
UI component catalog to be created @Ben
@Devs:Ask in code reviews to update the components page.
Organize dev talks and add confluence pagefor any new components created