Confirmed users
230
edits
Gaia/Architecture Transition Proposal: Difference between revisions
Jump to navigation
Jump to search
Gaia/Architecture Transition Proposal (view source)
Revision as of 14:31, 20 March 2015
, 20 March 2015→Impact on User Story
(Created page with "= Transition Proposal = This is a proposal to migrate our current codebase to the new and unified architecture for Gaia apps mentioned in the Gaia/Architecture Proposal|Arc...") |
|||
| Line 35: | Line 35: | ||
== Impact on User Story == | == Impact on User Story == | ||
All those teams can work concurrently, without having to worry about other teams. | |||
It creates an asynchronous development model for User Story. Usually a user story will impact the front-end and the back-end team. Those teams can work on the user story asynchronously, and one team may have done its related part while the other may have not started yet. | |||
But at some point, the front-end and the back-end needs to synchronized to validate the integration. | |||
Also both front-end and back-end may independently require to synchronize with the Toolkit. | |||
[[File:Gaia Transition Proposal Async Model.png]] | |||
The backlog of each team is scoped to the responsibility of one of the mentioned categories only. It should create more focused and smaller backlog for each teams, but require some additional synchronization. | |||
As an example the front-end and the back-end should be sure to have a shared deadline for a defined feature. | |||
But front-end and back-end may have custom deadlines to work on this feature, as long the deadline if not targeting after the shared deadline. | |||