2015-12-05 | Sprint retrospective #2 and sprint planning #3 online meetings

(Gualter Barbas Baptista) #6

The sprint retrospective is starting now and everyone on the team (@TDoennebrink, @toka, @josefkreitmayer, @wellemut, @Giuliana, @Silke, @species, @alabaeye, @rene, @iramollay, @amy, @elfpavlik, @simonline, @Michael, @EllenFriedman, @DagmarE, @kei, @DavidBollier, @gandhiano) is welcome to follow it on the live pad.

(Jon Richter) #7

@species @gandhiano The milestones fork seems to be working now:

Please make yourself comfortable with

if you intend to change the look and feel of the site. Else feel free to play around with

(Josef Kreitmayer) #8

@gandhiano I want to strongly argue for not using the “close spint” function in taiga for the #2 Sprint, as it would delete all the current track-keeping, that e.g. is helpful for my related tasks that are underway.

Today I will not be able to join, but will ad 2 - 3 user stories to the backlog.

(Gualter Barbas Baptista) #10

For anyone interested, we are working on the user stories (leftovers from last sprint and backlog). This is the time/place to add anything you think is missing from the whole picture.

Feel invited to join our live notes and to check/comment on the TransforMap backlog.

(Gualter Barbas Baptista) #11

Today we did some backlog grooming, reviewing, refining and adding new stories by collaborating on the new very nice hackpad (tks @almereyda for deploying it!).

We want to invite all interested people in the TransforMap community (@Team @Scrum @Luca @kei @Simon_Sarazin, among others) to review the current backlog and help in refining existing stories or proposing new stories, until Tuesday 9:30 AM CET. You can do that by commenting, editing, or writing any stories on [that same hackpad]((https://notes.transformap.co/Scrum-Backlog-Grooming-2015-12-06-WxoErL4wmwd#:h=Stories-to-add-and/or-refine).

At 10 AM we then start the sprint planning meeting, where stories will be pasted to the backlog, prioritised and the next 2 weeks of work planned. Apparently with an enlarged team :slight_smile:

Please note that you need to register in order to edit, although you can always read it. Don’t worry about all that Dropbox stuff around - hackpad has been recently open sourced and this instance is hosted on our own infrastructure.

(Josef Kreitmayer) #12

can we help somehow with that?

would you like to join our backlog grooming?

We are in mumble

(Josef Kreitmayer) #13

@toka would you join the Taiga Board, that would help a lot with task-oriented communication:


(Paul Mackay) #14

@josefkreitmayer are you preferring general discussion to be here and core team comms in Taiga? Just wondering as I cannot see a way to add comments there. Just checking.

(Thomas Kalka) #15

sorry, currently i wont add another tool to my stack …

(Thomas Kalka) #16

@Scrum currently I feel somehow like hijacked by CHEST and SSEDAS. Could you think about separating transformap goals and work towards them of project specific topics ?

(Gualter Barbas Baptista) #17

Can you a provide a concrete example of what you mean by a Transformap goal which is not currently represented by the stories in the backlog?

(Thomas Kalka) #18

That is not the problem. The backlog is a mixture of project specific tasks and transformap specific tasks.
Decisions done for transformap in all this other communication channels (taiga, trello, hackpad, etherpad) are not transparent for this discourse public.

(Gualter Barbas Baptista) #19

CHEST is a funding that directly emerges from efforts of the broad TransforMap community and therefore I see no mismatch between “project specific” and “transformap specific”. It also underwent, to the extent of my knowledge (I was less involved in TransforMap then) a legitimate work and decision making process.

SSEDAS is a service delivery to a consortium of organisations related to solidarity economy. It was not, to the extent of my knowledge legitimately agreed and openly discussed in the TransforMap community. I basically started my active contributions to TransforMap when this issue emerged, so got very involved in the whole story.

Now, while I understand your point that you find a mix of specific SSEDAS stories and TransforMap ones, I would still argue that:

  1. the process is transparent to this discourse public, just that it might not be yet enough to address the and efforts are being made to make it clearer to everyone (e. g. regular communication, an introduction to the process, etc.)

  2. at the moment I see as problematic a separation of the “project-specific” stories and the TransforMap stories. For me, the point is that projects and fundings should contribute, to the extent possible, to support the developments that the TransforMap community finds as prioritary. Separating it, would mean that it we will have a team focused on delivering products to partners, parallel non-matching developments, etc. For example, I like to see SSEDAS as a real-world testbed TransforMap technologies

  3. Everyone is invited to formulate new stories (on the hackpad) and to join the team (on Tuesday, or the next sprint planning meeting). Those who are on taiga (and everyone can be, just ping me) can also vote stories up or down, helping to settle a list of priorities on which the scrum team (which should respond to the community needs, not singular projects) will work on.

If, in the future, more people are engaged, we can have a second team and get e.g. SSEDAS split apart, because it has in fact a few deliverables which are hard to make matching with TransforMap’s own vision. But at least for the next iteration I don’t see a sense in separating this.

(Jon Richter) #20

Actually it doesn’t even diverge too much of our vision and even extends it to a concrete perspective where a minimal, but complete narrative seems appropriate. It’s just one of the other communities that work with us, but contributing resources to the overall process and thus something like a well welcome plugin.

(Josef Kreitmayer) #21

@toka, I found a quote by @almereya, that basically describes my 5 cents.

Even though, I see CHEST and SSEDAS speparated, and also see, that I would not put too much community related aspects in the sprint, but would like to (re-)activate the circle structure, we developed in Potsdam, I think, too many separations just create more namespaces and entities to take care of.

(Gualter Barbas Baptista) #22

The sprint planning meeting is starting on Mumble (server voip.open-resource.org).

@scrum @kei @Luca @toka

If anyone has difficulty in joining please ping me.


10:00-10:30 - Adding new/revisioned stories from the hackpad to the backlog
10:30-11:00 - Voting and prioritizing stories (everyone welcome to, also those not taking part @Team - just need your address to invite to Taiga)
11:00-12:40 - Planning poker
12:40-13:00 - Setting the sprint

There is no pad or live notes on the sprint planning meeting. If you want to passively follow, keep an eye on the taiga project timeline

(Gualter Barbas Baptista) #23

Voting on stories

In the next half an hour we will be voting to help get the most important stories for a larger number of people to go up. Most voted stories are more probable to be taken by the @scrum team to the next sprint(s).

Feel welcome to cast your vote on any stories of the backlog now

Note: to cast a vote you need to enter the user story and then on the top left you have a number (number of votes) with an arrow up (add your vote) or possibly down (remove your vote)

(Gualter Barbas Baptista) #24

We are nearly finished with the planning part. @kei would you be able to join again now, so that we can refine and estimate efforts on the landing page story?

We are working on refining this on a new hackpad document, which can also be further used as a document to further structure/document/develop the landing page concept

(Gualter Barbas Baptista) #25

We have a new sprint!

As some team members were not present, we made the choices of what stories to include based on previous stated wishes. If you have an opposition to the inclusion of some story, or absolutely need to get another in, please discuss it here.

Welcoming @kei on the @scrum team!

Merry Xmas sprint or walk! :santa: :evergreen_tree: :mushroom: :runner: :walking:

(Josef Kreitmayer) #26

@gandhiano and @species I want to appologize for my short appearance today at the sprint planning meeting. As I am a little sick, and also a little bit overwhelmed with personal and work related tasks before boarding the plane to india on thursday 7:00 am. I am sorry for the way I behaved, and am really happy, that we saw it would be better that I leave the meeting again.

##I am very happy with the outcome by the way.
##I am very happy, that we can continue working on the tasks started in the last sprint.

##I am as well very happy to welcome @kei on board.

Thank you both @species and @gandhiano for being at the bridge.