Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
Hi I am currently in a Scrum Team where the Scrum Master and Product Owner exclusively decide which stories a team will work on for a sprint.
They are also exclusively responsible for analysing the accuracy of estimations and measuring velocity.
I am in favour of giving this responsibility to the team but I would like some unbiased opinions on the approach, pros/cons etc.
I recommend a review of the scrum guide for a truly unbiased view. It's available from here : http://scrumguides.org/ The scrum guide is very clear on the separation of roles in the areas you've mentioned.
The product owner is responsible for the product backlog, including it's ordering.
The estimation of the items in the product backlog is the responsibility of the people doing the work (ie: the development team).
The selection for work to be taken in to a sprint is a collaboration between the product owner and the development team.
Velocity is a measure of the work completed in prior sprints. It doesn't need to be measured. It simply 'is'.
You sholud do it togehter as a Scrum Team. It's true that PO set business priorities but also there can be some technical blockers and dev team can support PO in that field. SM shouldn't make dacisions - his role is to support both, developers and PO to find best solution.
About velocity and estimations, that's is also part of SM work to help you identyfy your problems, ex with estimations and in general planing and analysing data helps here a lot to check if your estimations are ex too optymistic
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
i've found many publications that talks about to find Traceability Links and how store them into matrix or other data structure like XML.
I'd like to know if you know any publication on how traceability links are used.
Thanks
A high level (i.e. short) answer is given on the german wikipedia:
With the help of traceabilty data it is possible to measure the quality and progress in a systems development project. This is espicially relevant for the development of security critical systems, as legal requirements such as ISO 26262 or Automotive Spice require traceability to proof that security critical requirements have been implemented and tested in adequate quality. Furthermore, traceability makes impact analysis easy.
refer to https://de.wikipedia.org/wiki/R%C3%BCckverfolgbarkeit_(Anforderungsmanagement)
Fore a more commercial view, you may want to look at the benefits promised by dedicated traceability tools, such as
Validate your links and requirements after every change to be sure to achieve consistent traceability and unsuspicous links.
or
Visualize artifacts and their relations for a clear overview. Navigate between interrelated artifacts with a simple mouse-click and analyze their dependencies.
(In this case cited from https://www.itemis.com/en/yakindu/traceability/ )
Try the following:
Karl Wiegers, Software Requirements 2nd edition, Microsoft Press, p. 357 f.
ISBN 978-0-7356-1879-4
Wiegers emphasizes the use of traceability links in
Certification of software
Change impact analysis
Maintenance
Project tracking
Reengineering
Reuse
Riskreduction
Testing
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Gathering requirements is an essential stage creating software or web applications.
I have searched the web extensively without finding any directions on how to elicit requirements for personal projects. All information i found - including books i read - is focussing on different stakeholders.
So i´m wondering, what would be the best way to 'gather' the requirements for personal projects?
I can't imagine i'm the only one with this question. I have plenty of ideas for webapplications. Since i am the only stakeholder at this time - no users are identified yet, i need to develop a couple of applications for personal use - i find it hard to interview my self to elicit those requirements.
As English is not my native language, apologies for possible textual errors.
You can have a document with all the information you have in your head of the project in a bullet list format called "Project Memoir". Just list all the information & business rules you need to put in the project. You can after that start developing a kind of informal Software
requirements document (as it's for a personal project) containing some essential information for you in the development phase, like a feature list with their description, use cases & scenarios that will help you in testing in later phase, mock up screens for defining the UI look & elements, data elements lists for defining screen contents. Just keep it simple & easy as it's for only your personal use.
Hope that would help :)
The questions are supposed to be a trigger of a thought process.
What makes it any different in case you are the developer next to the stakeholder? Your thoughts are those of a stakeholder and you will have to try to identify your own requirements by this process.
Identifying your own requirements with a structured approach will help you identifying requirements that you would otherwise have encountered during development.
If the sole purpose is not only personal, I doubt whether it is a good idea to start developing. Then you will need to find prospects to interview. Investigate the possible markets.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
It sounds strange, but that's what I need. An effective way to document a Scrum project.
I agree that it's a waste of time to produce User Stories and a Requirements Documents.
But sometimes we need to have the vision of how the software currently works.
How do you do that? Do you know some best practices or case scenarios on this?
Thanks
The short answer is this: you can write anything you want or need to about any project, Scrum or otherwise. Scrum doesn't tell you how to document, but it doesn't tell you not to. The way you document is in itself irrelevant to Scrum.
That said, if you need to understand how the software currently works, a document will not help you. Documentation often lies. If you're trying to understand how the system works, a document will only tell you what people think or want to believe is the truth.
What you should consider, is to use executable specifications and Test Driven Development to prove that what you believe the software does is actually true. automated tests combine documentation, examples and regression tests all into one offer.
There are several kinds of documentation that can help you. It depends on your context which ones you need, and at what detail level. You could also use a tool such as MOOSE to create project specific visualizations of your software at all levels. Some simple documents are:
A story map
Gherkin style high-level features and scenarios
If you've tracked your product backlog items through completion, including acceptance criteria for each you should be able to point to the list of completed product backlog items as documentation. Everything you've programmed should be associated with a PBI, so the completed PBI's document your project.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I've been trying to describe the concept of platforms to some non-developer people on my team. I'm trying to explain how platforms are more than just tools and environments. For example, the Facebook Platform. How to describe the fact that the platform is more than just the website, but includes protocols like XFBML, opengraph, etc.
Facebook Platform is one example, but I would be interested if anyone has an abstracted way to describe what 'platforms' are in the tech world. I've had difficulty explaining this concept before in situations unrelated to flash.
Analogies that aren't tech related would be helpful as well.
I would say something about it being all-inclusive and extending to include all functionality that the entire ecosystem around that particular piece of software needs to thrive.
The Wikipedia page might help in putting it into words: http://en.wikipedia.org/wiki/Computer_platform
I use a "restaurant" metaphor, myself: Think of the kitchen, the bar, the dining room as components to the platform. How the decor can change in the dining room without changing the function, but can affect how customers perceive the business. How the recipes instruct the cooks, and the interactions with the wait staff can all affect different aspects of the business much like different pieces of your platform can be modified to affect different aspects of your business. Oh, and don't forget management!
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
Based on the different views documented in SAD which RUP roles should should be responsible for creating the SAD? I thought from the beginning that the SAD was only for a technical audience but from what i can see in RUP it is more than that so it seems like it is not only the Software Architect that should be involved.
Well, according to RUP's documentation, it's the Software Architect.
Quoting the Artifact: Software Architecture Document online reference:
Responsibility
A software architect is responsible
for producing the Software
Architecture Document, which captures
the most important design decisions in
multiple architectural views.
The software architect establishes the
overall structure for each
architectural view: the decomposition
of the view, the grouping of elements,
and the interfaces between these major
groupings. Therefore, in contrast with
the other roles, the software
architect's view is one of breadth, as
opposed to depth.
The software architect is also
responsible for maintaining the
architectural integrity of the system
through the development process by:
Approving all changes to architecturally significant elements,
such as major interfaces, described in
the Software Architecture Document.
Being part of the "change-control board" decisions to resolve problems
that impact the software architecture.
Well,
Do not think "roles" as job titles...
If you work in a traditonal enviroment, generally there is a guy who is job title is also "Software Architect"...If you work in an agile enviroment generally you can not find a job title like "software architect" in team...So the important thing is who knows and who gives the important decisons about architecture: Who fills the role of the architect not title....
In an healty enviromement[ traditional or agile] one guy can not give all decisons, so SAD is a workproduct of all team in practice because all teams members sometimes play the role of "architect"...