Latest Job Opportunities in India
Discover top job listings and career opportunities across India. Stay updated with the latest openings in IT, government, and more.
Check Out Jobs!Read More
🔥 Transfer stories from good to wonderful
revealed
Ask how stories are written in a graceful or scrum environment, and you will inevitably get “as a … I want …, so …” “swamps answer, cookies clips. But ask yourself this, is this all you write in a story?
User stories in the Agile world are a way to achieve a goal in software applications. Definition of the umbrella, if I may pray, it is Vice -manner for the conversation. We say that the stories are a shorter, more lighter and lighter version than capturing work requirements, while never, they are never intended to replace a good conversation.
This is an ideal introduction to a modern legend: you do not need to write the user’s stories with the format of the standard work requirements document, with cases of use, UML / Sequney / State Plans, compatibility matrix and all its glory in the ancient world …. which means that they do not need to write it at the same level of rigor. Anyone who can mobilize “K .. I want ..” can write the user’s stories.
In fact, rigor is completely practiced, if not more than the requirements in the traditional sense; Accuracy and discipline are actually found in documents coordination but in the content. After I wrote users’ stories for years in ThinkWorks, there is a set of principles that really help me convert stories from good to wonderful.
1. Get your right story
As an editor,
I want to create drafts for my articles before publishing,
So that I can present them to the editor -in -chief for the amendments before my articles come out.
I have lost dependence on projects where the stories are incomplete. How many times have you seen the “so” missing? It is often the most difficult part of the entire story, and many people Just leave it. Do not make this error. The story format has been placed like this for a very good and real reason. It is very difficult to obtain this part correctly, not to mention having this part, because it forces the author to think hard about the reason for this story, and the reason for existence. It justifies why the company must spend its money to develop this on another story. Which means that if there is no real reason for its existence, the priority will be completely canceled or deleted. However, if you delete this part, there is a very little report of reporting the true value it provides. It will be just a list of wild desires mixed with legitimate needs and needs. It also encourages behaviors such as “whoever screams with the highest voice gets most of the stories they want” – the matter ended in this position is a sad place to be really.
Another hate is a “user” vision for all hundreds of stories. Do you only have one user? truly? Only one type? No one at all? … I will leave this gracefully for another period.
2. The non -written rule of what is going on inside
I always have in the ready -made menu, regardless of the field I work. The menu contains cornerstone stones that tell you whether your stories have the minimum information sufficient to express what you want to do, for the development team:
- Story: As I want, so
- a description
- Assumptions
- Technical notes
- Out of range
- Admission criteria
- appreciation
- Priority
It really passes through the list if you have collected enough information to start development. It is no longer acceptable to write half -baked ideas and deny them as requirements, under the Agile or Scrum brand. Please, do not blame Agile or Scrum when you are really lazy; To be graceful does not mean that we have any less interest in detail. It focuses on the appropriate level of details in the right places at the right time.
3. Choose your words carefully
While you write less, I really mean what you say when you say. Ensure that you use the same domain language and not add another collar for the team to jump. When you write stories, make sure that you indicate the terms properly and fixed. The word graph was used? Do not turn into the words of the scheme in the middle of the Kasbah. Even if it means the same things or the like, it will not always be for someone else. I have some other examples:
- Photo against the image for the clarification against the graph against the graphs
- The description versus the content versus the Blurb versus CUB against the paragraph
- The number for the number for the letter
- Table for the graph
The same applies to when you speak to QAS, developers, product managers and stakeholders. Be aware that terms and names are used to plan the field model, and live in the code database as well as unit tests, job tests and comprehensive tests … So the consensus will only help everyone to understand what it means clearly.
4. Use shortcuts slightly
Do not build the barrier in front of the connection above by placing loads and a lot of shortcuts (even known). Understand one person for CMS, CRM, GDP, SAT, sitting completely different from someone else.
5. The agreement Excessive cooperation
In life and in writing the story, use simple English as possible, strive to use this rule as possible. There is no better way to put this.
Whether you want to admit it or not, no one wants to read Reams and Reams of Waffle when they really search for boiled facts – so I only show boiled facts – and show them clearly. Many analysts grow in frustration or frustration, or both, when they discovered that someone was really reading their documents. Worse, many misunderstanding and misunderstanding stems from the fact that implicit requirements are hidden in the paragraphs of the text when they must be clarified clearly a line line. Be clear, unambiguous and brief in your words. Adding unnecessary terms for things can not be confused only by people, and everywhere: words such as frame, warehouse, structure, and XYZ manager when name are smart features but they really build towards the fluff that people learn to ignore. Horror shock, no (!)
I hope this is useful. As with most things in a cooperative environment, ask for notes from your peers if you are not sure of the correct level of details; You never know, a few comments have a long way in the world of continuous learning 🙂
👉 Read more at: Read Now
Explore more: #Transfer #stories #good #wonderful
Written by Jenny Wong on 2011-08-09 06:40:00
Source Feed: Agile is an attitude, not a job title
🔥 Transfer stories from good to wonderful
uncovered
Ask how stories are written in a graceful or scrum environment, and you will inevitably get “as a … I want …, so …” “swamps answer, cookies clips. But ask yourself this, is this all you write in a story?
User stories in the Agile world are a way to achieve a goal in software applications. Definition of the umbrella, if I may pray, it is Vice -manner for the conversation. We say that the stories are a shorter, more lighter and lighter version than capturing work requirements, while never, they are never intended to replace a good conversation.
This is an ideal introduction to a modern legend: you do not need to write the user’s stories with the format of the standard work requirements document, with cases of use, UML / Sequney / State Plans, compatibility matrix and all its glory in the ancient world …. which means that they do not need to write it at the same level of rigor. Anyone who can mobilize “K .. I want ..” can write the user’s stories.
In fact, rigor is completely practiced, if not more than the requirements in the traditional sense; Accuracy and discipline are actually found in documents coordination but in the content. After I wrote users’ stories for years in ThinkWorks, there is a set of principles that really help me convert stories from good to wonderful.
1. Get your right story
As an editor,
I want to create drafts for my articles before publishing,
So that I can present them to the editor -in -chief for the amendments before my articles come out.
I have lost dependence on projects where the stories are incomplete. How many times have you seen the “so” missing? It is often the most difficult part of the entire story, and many people Just leave it. Do not make this error. The story format has been placed like this for a very good and real reason. It is very difficult to obtain this part correctly, not to mention having this part, because it forces the author to think hard about the reason for this story, and the reason for existence. It justifies why the company must spend its money to develop this on another story. Which means that if there is no real reason for its existence, the priority will be completely canceled or deleted. However, if you delete this part, there is a very little report of reporting the true value it provides. It will be just a list of wild desires mixed with legitimate needs and needs. It also encourages behaviors such as “whoever screams with the highest voice gets most of the stories they want” – the matter ended in this position is a sad place to be really.
Another hate is a “user” vision for all hundreds of stories. Do you only have one user? truly? Only one type? No one at all? … I will leave this gracefully for another period.
2. The non -written rule of what is going on inside
I always have in the ready -made menu, regardless of the field I work. The menu contains cornerstone stones that tell you whether your stories have the minimum information sufficient to express what you want to do, for the development team:
- Story: As I want, so
- a description
- Assumptions
- Technical notes
- Out of range
- Admission criteria
- appreciation
- Priority
It really passes through the list if you have collected enough information to start development. It is no longer acceptable to write half -baked ideas and deny them as requirements, under the Agile or Scrum brand. Please, do not blame Agile or Scrum when you are really lazy; To be graceful does not mean that we have any less interest in detail. It focuses on the appropriate level of details in the right places at the right time.
3. Choose your words carefully
While you write less, I really mean what you say when you say. Ensure that you use the same domain language and not add another collar for the team to jump. When you write stories, make sure that you indicate the terms properly and fixed. The word graph was used? Do not turn into the words of the scheme in the middle of the Kasbah. Even if it means the same things or the like, it will not always be for someone else. I have some other examples:
- Photo against the image for the clarification against the graph against the graphs
- The description versus the content versus the Blurb versus CUB against the paragraph
- The number for the number for the letter
- Table for the graph
The same applies to when you speak to QAS, developers, product managers and stakeholders. Be aware that terms and names are used to plan the field model, and live in the code database as well as unit tests, job tests and comprehensive tests … So the consensus will only help everyone to understand what it means clearly.
4. Use shortcuts slightly
Do not build the barrier in front of the connection above by placing loads and a lot of shortcuts (even known). Understand one person for CMS, CRM, GDP, SAT, sitting completely different from someone else.
5. The agreement Excessive cooperation
In life and in writing the story, use simple English as possible, strive to use this rule as possible. There is no better way to put this.
Whether you want to admit it or not, no one wants to read Reams and Reams of Waffle when they really search for boiled facts – so I only show boiled facts – and show them clearly. Many analysts grow in frustration or frustration, or both, when they discovered that someone was really reading their documents. Worse, many misunderstanding and misunderstanding stems from the fact that implicit requirements are hidden in the paragraphs of the text when they must be clarified clearly a line line. Be clear, unambiguous and brief in your words. Adding unnecessary terms for things can not be confused only by people, and everywhere: words such as frame, warehouse, structure, and XYZ manager when name are smart features but they really build towards the fluff that people learn to ignore. Horror shock, no (!)
I hope this is useful. As with most things in a cooperative environment, ask for notes from your peers if you are not sure of the correct level of details; You never know, a few comments have a long way in the world of continuous learning 🙂
🔗 Read more at: Source
Explore more: #Transfer #stories #good #wonderful
Authored by Jenny Wong on 2011-08-09 06:40:00
Source Feed: Agile is an attitude, not a job title
