Timeline for How to structure our organization and define agile teams in a multiple concurrent projects context?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 3, 2019 at 20:09 | history | edited | Tiago Cardoso | CC BY-SA 4.0 |
Restructured question, breaking down between "common" problem to "specific" problem (to increase usefulness to the community)
|
| Nov 2, 2014 at 20:01 | history | tweeted | twitter.com/#!/StackProjects/status/529000339886714880 | ||
| Oct 31, 2014 at 17:51 | answer | added | Bharath Suryakanthan | timeline score: 0 | |
| Oct 17, 2014 at 17:26 | comment | added | Damien Salle | This is what I understood as an important concept: if you want to reduce context switching and gain in eficiency and agility, you should be focused... thus my understanding of working on only 1 project. Maybe the correct thinking should be "one concurrent project only" or "one project only in a sprint"? ??? What do you think then? | |
| Oct 17, 2014 at 13:58 | comment | added | user16583 | Why do you feel you <i>have to</i> associate each member with only one project? Agile means being flexible and responsive rather than rigidly shoehorning people into different silos. | |
| Oct 17, 2014 at 9:41 | answer | added | SpoonerNZ | timeline score: 0 | |
| Oct 14, 2014 at 13:38 | answer | added | Ashok Ramachandran | timeline score: 4 | |
| Oct 13, 2014 at 11:10 | history | asked | Damien Salle | CC BY-SA 3.0 |