Not logged in. · Lost password · Register

Page:  1  2  3  next 
Dirk Riehle
Avatar
Member since Sep 2009
291 posts
Subject: AMOS SS14 Q&A with Lecturers
Please use this thread to ask administrative questions on AMOS.

For self-help questions among students please use the "Agile Methods and Open Source" subforum.

We will monitor this forum and try to respond in time.
http://osr.cs.fau.de
Ann Barcomb
Member since Apr 2014
37 posts
Subject: Mid-term Release Plan
One team emailed me some questions about the mid-term release plan, which according to the schedule should be included in the planning artifact due on 1 May.  The paraphrased questions were: will there be additional information given in the project management lectures, is it possible to see the slides before the lecture so that there is more time to do the release planning, and how is the planning graded?

The answer to the first question is yes.  For the second question I will refer this to Prof. Riehle, but I will note that one resource which is available to you whenever you want to see examples are the AMOS projects from previous years, many of which can still be found on Github.  For the last question, let me note that agile development is designed to deal with a changing situation.  Therefore I don't expect your planning to be completely accurate, only realistic.  Over time, I expect to see improvements in the planning process as your team becomes more experienced and applies all parts of the process, including the retrospective.
Dirk Riehle
Avatar
Member since Sep 2009
291 posts
Hello everyone,

I expect to have the slides teaching release planning out soon so you can look at them before the deadline.

Realizing time is short, I already postponed the mid-term release planning by one week so you should have sufficient time to do the planning based on the available materials.

Thanks,
Dirk
http://osr.cs.fau.de
Lara Powollik
Member since May 2014
4 posts
Subject: SCRUM Master Role
Hello everyone,

amongst several teams, there is confusion about assigning the SCRUM Master role. During the past couple of weeks we have heard conflicting feedback. Should this role be taken by developers at least once or is this only a PO role?

Thanks,
Lara
Ann Barcomb
Member since Apr 2014
37 posts
Subject: Re SCRUM Master Role
The last time we did the AMOS class we asked that everyone take the role of the Scrum master at least once, although teams might choose to give this role more often to the POs because the Review & Release manager role is only taken by the SDs.  However, we did indeed have some internal inconsistency on this point this year, so in checking the planning documents I have not been looking to see if each person has taken the role but only if the roles are to some extent rotated.
Lara Powollik
Member since May 2014
4 posts
In reply to post #3
Subject: Mid-term release
Thank you for your feedback, Ann.

We have another question concerning the mid-term release. Does this have to include any special tags? Will teams present their releases in class or is it our own responsibility to inform our industry partners? Is there anything else we should know?

Thanks,
Lara
Sabine Aschenbrenner
Member since May 2014
2 posts
Subject: Release Plan
Hello,

we have some questions concerning the release plan.

How detailed are we supposed to plan our next sprints?
Should we already plan the user stories for each sprint?
For our project, it seems to be very hard to plan that detailed and in the end we are pretty sure that we cannot stick to the plan, which we would be able to do now.

Are we (as POs) supposed to estimate the sizes of the sprints? Isn't it correct to write the sizes from the planning poker into the estimated size column of the release plan?

Thanks,
Sabine
Ann Barcomb
Member since Apr 2014
37 posts
In reply to post #6
Subject: Re Mid-term release
Quote by Lara Powollik:
We have another question concerning the mid-term release. Does this have to include any special tags? Will teams present their releases in class or is it our own responsibility to inform our industry partners? Is there anything else we should know?

The answer to your first question can be found in either the slides 02B - Server Setup (on StudOn) or in the Deliverables Checklist (linked from the Course Index).

For your second question I will ask Prof. Riehle to answer.
Ann Barcomb
Member since Apr 2014
37 posts
In reply to post #7
Quote by Sabine Aschenbrenner:
How detailed are we supposed to plan our next sprints?
Should we already plan the user stories for each sprint?
For our project, it seems to be very hard to plan that detailed and in the end we are pretty sure that we cannot stick to the plan, which we would be able to do now.

At this point you should have a release plan for the mid-term release completed.  The final release plan is due the same week as the mid-term release.  Release plans should be created by assuming that the team will continue to work at the pace which has been established and planning the appropriate number of story points for each sprint.  You might check the student discussion board as well, as one team shared their experience there.

Of course you will discover that the plan changes.  Maybe the team couldn't complete everything one sprint, or a story was overestimated, or priorities have shifted.  This is fine.  In slides 03C - Development Planning, the release plan is described as evolving.  You will have to check it every week to ensure that it still reflects your best guess about the project's future development.

A release plan is not a promise that you will deliver exactly what is written there.  It is a reasonable prediction based on experience.  Over time, the team should become better at estimating story points (if real and estimated effort remain far apart, this should prompt discussion) and also at completing a fairly consistent number of story points each week.

Quote by Sabine Aschenbrenner:
Are we (as POs) supposed to estimate the sizes of the sprints? Isn't it correct to write the sizes from the planning poker into the estimated size column of the release plan?

The actual estimate which you use when the task is accepted by the software developers and moved into the Sprint Backlog is based on planning poker and the input of all software developers.  However, as a PO, you want to get some idea of how large the tasks are before you enter the planning meeting.  This allows you to do some planning, and also to revise stories which turn out to be bigger than you thought.

This is alluded to in slide 19 of 03C - Development Planning and in slide 29 of 03A - Process Management and explicitly mentioned in the Deliverables Checklist.

Ideally over time the SDs are becoming better at estimating and also the team is converging on a shared understanding of story points, so you should be able to ask any SD for a pre-planning estimate.
Dirk Riehle
Avatar
Member since Sep 2009
291 posts
In reply to post #6
Will teams present their releases in class or is it our own responsibility to inform our industry partners? Is there anything else we should know?

The purpose of the mid-term release is to have a product release (experience) before the real product release experience (the final release).

Key aspects of a product release are that you (a) actually release (you can decide not to release a sprint, not release the product means you didn't manage well towards a stable version and (b) your release plan is in order, cleaned up, and a good record of what happened.

(a) is the most important part. The most obvious mistake is to keep pushing ahead like in any prior sprint and not focus on having a stable version. If you do that, you may not be able to release, and your software remains riddled with bugs.

So, you release. To the industry partner it doesn't matter, unless you decide to take the time for an extra session. They should always be able to find the latest version for testing at osr-amos.cs.fau.de

There won't be any presentation in class. Demo day is the last day of class.
http://osr.cs.fau.de
Dirk Riehle
Avatar
Member since Sep 2009
291 posts
In reply to post #9
Ann already answered this:

Are we (as POs) supposed to estimate the sizes of the sprints?

I'd like to add that for estimating features that are for later sprints, the POs can do it, though typically, the POs sit down with a senior developer and go through the features for the remaining sprints. It is obviously not going to be as good as if you played planning poker, but it is typically good enough and doesn't require the full team.
http://osr.cs.fau.de
Ann Barcomb
Member since Apr 2014
37 posts
Subject: Verify your Git repository before the deadline
We know that for many of you, Git is new, which means it is easy to make mistakes.  Twice we've seen instances where teams thought their projects were available, but the new material wasn't actually part of the master.  Hannes and the Git lecture slides can offer advice on resolving problems, but first you need to be aware that there is a problem.  Therefore it is highly recommended--if you are unfamiliar with Git and responsible for deliverables--that you clone a fresh copy of the repository and verify that it looks as expected.  Try the following steps for verification:

Create a clean temporary directory
Clone your repository
Make sure all necessary branches and tags were fetched
Make sure that the tagged commits contain the right files and are indeed the version you want to release
Try to build your fresly checked out repository
ferdi0807
Member since Nov 2013
51 posts
Hello @ all,

quick question about the final release plan:

Are we supposed to make the final release plan only for the sprints 8-13 or one big one including all sprints (also those that have already been in the mid-term release plan)?

thanks in advance! :-)
Ann Barcomb
Member since Apr 2014
37 posts
Quote by ferdi0807:
Hello @ all,

quick question about the final release plan:

Are we supposed to make the final release plan only for the sprints 8-13 or one big one including all sprints (also those that have already been in the mid-term release plan)?

thanks in advance! :-)

The final release plan covers the sprints following the mid-term release, to the end of the class (8-13).
Dirk Riehle
Avatar
Member since Sep 2009
291 posts
In reply to post #13
Are we supposed to make the final release plan only for the sprints 8-13 or one big one including all sprints (also those that have already been in the mid-term release plan)?

We view the mid-term and the final release as two distinct releases.

Hence the release plan for the final release should only cover the second release.

Cheers,
Dirk
http://osr.cs.fau.de
Close Smaller – Larger + Reply to this post:
Verification code: VeriCode Please enter the word from the image into the text field below. (Type the letters only, lower case is okay.)
Smileys: :-) ;-) :-D :-p :blush: :cool: :rolleyes: :huh: :-/ <_< :-( :'( :#: :scared: 8-( :nuts: :-O
Special characters:
Page:  1  2  3  next 
Go to forum
Datenschutz | Kontakt
Powered by the Unclassified NewsBoard software, 20150713-dev, © 2003-2011 by Yves Goergen