April 30, 2010 6:00 PM - 7 attended
AgileWorks & Software Business Incubator: Retrospectives
Timisoara Software Business Incubator (map)
All (if not most) Agile iterations have to end with a retrospective, on how things have evolved, problems encountered, new things that should be tried and so on. AgileWorks and Software Business Incubator is hosting a meetup that is about how are we doing retrospectives, how we should do them, if and how do we change things after a retrospective and, last but not least, how do we learn from our mistakes.
-
-
Flavius Stef
Sure, it would be interesting to share experiences related to code management.
Posted April 27, 2010 at 10:47 PM -
Lucian Daniliuc
Meetup review:
- the best and only way that the team and process can improve;
- retrospectives are not sprint reviews;
- the team can send suggestions and tips anonymously and before before the meeting;
- team should write down the facts about the retrospective and then they should talk about it;
- the action plan is absolutely necessary: it is the decision that will change the next sprint;We also discussed about source code control, communication in a team and testing.
Posted May 6, 2010 at 11:38 AM
-
-
Flavius StefEvent HostAssistant OrganizerGreat chat with a group of talented and determined people.
-
-
-
-
-
Offer a perk for our members and get exposure.
Offer a perk →
If there is time I would propose a second topic for the meeting (or for another meeting): source code control/release workflow on Agile teams.
To be more specific: How do you organize source code, which are the code commit roles of the team, who decides on merging/commiting into main branch, do you have a merge window stabilization stage, who and how reviews code, do you work with parallel repositories/branches, how often do you release, how much time do you need to release, etc.