user-stories | 易学教程

Azure devops, inherited process, cannot Add new completed state VS403093

阅读更多关于 Azure devops, inherited process, cannot Add new completed state VS403093

问题 When I try to add new completed state to user story or task in inherited process of my azure devops project, I get the following error : VS403093: Team Services currently does not support changes to 'Completed' category. Choose a different category. I have looked all over the web and it seems like this is the desired behaviour as mentioned in this link, which I think is very weird. Are there any workarounds? I want to create a Done state for my work items, and I think that it's dumb to keep

Azure devops, inherited process, cannot Add new completed state VS403093

阅读更多关于 Azure devops, inherited process, cannot Add new completed state VS403093

User stories - Card, conversation and confirmation [closed]

阅读更多关于 User stories - Card, conversation and confirmation [closed]

问题 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 2 years ago . I don't understand a thing about the Card, Conversation, Confirmation formula for user stories. I don't understand if the conversation and confirmation part must be written down or they remain as a dialogue, in particular the CONVERSATION part. To be clear: is it right if a

From user stories to sequence diagram

阅读更多关于 From user stories to sequence diagram

问题 I would like to know: how to convert users stories into sequence diagrams? and what is the most easy diagram to understand (for customer)? 回答1: In my opinion, what works best with the customers are not use cases. They are too abstract and complicated even for the most of developers. And when they are finally approved, you're never sure whether the customers actually understood them correctly. I suggest the mix of UML activity diagrams and user interface prototypes (non UML) as far the best

User Stories - Problems that can't be made user stories [closed]

阅读更多关于 User Stories - Problems that can't be made user stories [closed]

问题 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 2 years ago . I am from an XP background. I know the process very well and have solid working experience with it. I have found it to be the best way to develop software. I find myself in the position of a process doctor of sorts and this creates much self examination and revaluation of my

How to write User Stories for technical implementation details? [closed]

阅读更多关于 How to write User Stories for technical implementation details? [closed]

问题 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 2 years ago . I'm trying to work in a more organised way and started adopting user stories. I think I have misunderstanding of how should I use user stories for technical stuff. Let's say I'm coding an app that gives me the ranking of my site for a certain Keyword in Google. The user story

From user stories to sequence diagram

阅读更多关于 From user stories to sequence diagram

I would like to know: how to convert users stories into sequence diagrams? and what is the most easy diagram to understand (for customer)? Aleks In my opinion, what works best with the customers are not use cases. They are too abstract and complicated even for the most of developers. And when they are finally approved, you're never sure whether the customers actually understood them correctly. I suggest the mix of UML activity diagrams and user interface prototypes (non UML) as far the best tool to work on this level of analysis with non technical business people. Activities model their

Scrum stories and behind the scenes features [closed]

阅读更多关于 Scrum stories and behind the scenes features [closed]

问题 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 2 years ago . As I understand things, the Scrum backlog is composed of a series of Stories that represent something for the end user and this is further decomposed into Features. If this is the case, where does all the behind the scenes features go that aren't really linked to a story but are still useful? For example, say I

Specific examples of Agile documentation? [closed]

阅读更多关于 Specific examples of Agile documentation? [closed]

问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed 2 years ago . In an answer to the question Documents for a project? , Chris Ballance replied that "User Stories" and a "burndown chart" are the two most useful types of project documentation for a developer. My question is, do you know of any good example[s], which I can see (for example on the

How to write User Stories for technical implementation details? [closed]

阅读更多关于 How to write User Stories for technical implementation details? [closed]

I'm trying to work in a more organised way and started adopting user stories. I think I have misunderstanding of how should I use user stories for technical stuff. Let's say I'm coding an app that gives me the ranking of my site for a certain Keyword in Google. The user story goes like that: As an Internet Marketer I want to find out where my website ranks for a keyword So I'll know whether my SEO efforts work Now this is pretty straight forward and user centric... However, what happens if I need to introduce Proxies into the loop. On one hand, Proxies are technical implementation detail on