Tag Info

New answers tagged

2

This is a good question. I don't have an official answer but where I work we add technical user stories and call them technical debt. If they weren't permitted, I would find some other way to get them added for the mere purpose of having my work recorded and communicated to the business. Likewise, having this documentation reminds us of what is needed for ...


0

You don't rely exclusively on point estimates for sprint planning anyway. During planning, your velocity can help you to quickly "propose" a sprint plan and/or assist with your sanity check before making the final commitment; but, no matter how much velocity data you have, the team ultimately needs to commit to stories, not points. Bear in mind, 5 x 1-point ...


1

Scrum Master do not give their status update, but they are there to facilitate the stand up meeting. Their role is to make sure meeting starts on time, everyone in the meeting gives their status updates within their time frame, take action when any team-member has roadblocks in completing their task. FYI, we are using our daily stand up meeting online at ...


1

My preferred method which I have been using for at least a few years now is to bump up the number after each story is completed. This means that the versions released at the end of the sprint will not be continuous, e.g. after 1.2.3 you might find 1.5.2 rather than 1.4.0. In the changelog you may either list the intermediate versions with their ...


2

If the classic semantic versioning scheme "MAJOR.MINOR.PATCH" makes sense, depends on to whom you deploy, and especially when and how often you deploy to the end user. The scheme is most useful if you work with stable release "4.5", where you start with as 4.5.0. The versions 4.5.1, 4.5.2, and so on contain only bug fixes, whilst you internally already work ...


4

For typical release management, you will want a build number being generated by your build system so that the DLLs are versioned every time they are deployed. This will ensure you can later check which version is deployed on a given server. Your 'marketing' version, which is usually put in release notes or published to your site should not be updated each ...


2

I would use build numbers. Usually a build number would correspond to the highest version of the version control system. If mondays build number was 1745 and there has been checked 5 changes in during tuesday, tuesday evenings build number would be 1750. Then make a short summary for what has changed between 1745 and 1750. Then every time you update the ...


2

It depends. Different agile teams have different processes because they have different needs. If you have a few dozen bugs coming in every day, an informal cube meeting is probably not going to cut it. If the majority of the bugs are user inputted, you need someone who just looks for dupes and can judge usability issues. If you're a small group, then ...


0

The first thing to say is that almost everything a Scrum team works on should be discussed in Sprint Planning meetings in the usual way. Whether a Story is a bug fix our new feature development, it is at this point that the Product Owner should put it in its place in a prioritised Sprint. Secondly, disruptions to Sprints do occur - it's just a question of ...


2

Triaging is not typically done as a meeting. Teams do it differently, depending on the product, but on our team, the product owner triages the customer issues, and we rotate another team member as "triager of the day" for issues that testing finds. The triager's job is not supposed to be debugging, but answering the following questions as efficiently as ...


6

The question, given your particular example, would be why does a developer want to develop a mechanism to store and retrieve images so that users can add/view images wherever required, unless a user wants to add or view images? That is, while your question is a good one, the example isn't. This is a user feature and should have a user story. And if the user ...


9

Technical stories are allowed, but I would advise you to try to avoid them as much as you can. For example, your story for saving and retrieving images can easily be written as two regular user-stories As a reviewer, I want my uploaded photos to be stored persistently, so that other users can view them at any time. (Note that this assumes that in your ...



Top 50 recent answers are included