No tienes acceso a esta clase

隆Contin煤a aprendiendo! 脷nete y comienza a potenciar tu carrera

Review: communicate with your customer accurately

5/25
Recursos

En esta lecci贸n recordar谩s los conceptos que hemos estudiado hasta ahora. Ahora es tu turno, lee los t茅rminos y sus respectivas definiciones para reforzar tu aprendizaje.

Customer鈥檚 Inception Customer鈥檚 Inception is the customer鈥檚 initial idea to get software for various purposes.
User Stories A user story is the representation of an individual task the Software has to do, it is composed of smaller tasks, and it contains a title, a description, and a priority value.
Iterations as part of a development process A work period after which you get together with the customer, show her your work, and receive feedback.
Accurate Communication It is key to understand Customer鈥檚 requirements and avoiding mistakes.
Idea Brainstorming Is necessary to get good requirements that will create fantastic results.
Estimate The time you agree with your team to finish User Stories.
Iteration cycle This is a little work cycle that produces quality, working software.
Estimating the whole project Takes place when you decide the size of the complete project.
Reaching consensus in estimations This takes place when you have agreed on the length of the estimation with the entire team, after playing planning poker.
Planning considering priorities Takes place after having a meeting with the Customer and agreeing on the features that should be included in the next Iteration. It is the Customer鈥檚 decision to include certain features.
Milestone It is a major release when you show your Customer your working, functional Software and you expect to get paid for it.

Todos los conceptos est谩n relacionados principalmente con la gesti贸n, planificaci贸n y estimaci贸n de proyectos que se llevan acabo junto al cliente.


Contribuci贸n creada por Kevin Fiorentino con aportes de Erwin Alan Fr铆as Mart铆nez.

Aportes 31

Preguntas 2

Ordenar por:

驴Quieres ver m谩s aportes, preguntas y respuestas de la comunidad?

o inicia sesi贸n.

Customer鈥檚 Inception: Customer鈥檚 Inception is the customer鈥檚 initial idea to get software for various purposes.

User Stories: A User Story is the representation of an individual task the Software has to do, it is composed of smaller tasks and it contains a title, a description and a priority value.

Iterations as part of a development process: A work period after which you get together with the customer, show her your work and receive feedback.

Accurate Communication: It is key to understanding Customer鈥檚 requirements and avoiding mistakes.

Idea Brainstorming: Is necessary to get good requirements that will create fantastic results.

Estimate: The time you agree with your team to finish User Stories.

Iteration cycle: Is a little work cycle that produces quality, working software.

Estimating the whole Project: Takes place when you decide the length of the complete project.

Reaching consensus in estimations: Takes place when you have agreed on the length of the estimation with the entire team, after playing planning poker.

Planning considering priorities: Takes place after having a meeting with the Customer and agreeing on the features that should be included in the next Iteration. It is the Customer鈥檚 decision to include certain features.

Milestone: It is a MAJOR release, when you show your Customer your working, functional Software and and you expect to get paid for it.

Hi everyone:

Taking the learned, and, my experience. I want to share with you something that it asked me in a technician interview. The scrum framework is a within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.

I tell you, the framework scrum in a minute. All start with product owner who is a person that prepare the product backlog. In this picture, you look at this in the beginning. The product owner collect the information of the product backlog with the stakeholders. Then, the product owner deliver the product backlog to the scrum master. The scrum master do the sprint planning for get the sprint backlog. The sprint planning is a meeting with the product owner, scrum master and the team. The planning pocker gets the estimations of every spring. That is to say, it gives the priority to every user story gave by the product owner, inside the product backlog. All days must do scrum daily for knowing the progress of the project. This meeting is just with the scrum master and the team. To the finish, it delivers a product increment in a meeting called sprint review. These iterations called sprints and finish with we complete all the user stories and deliver the complete product.

In principle, this is applied to the development software, but it can be applied in any project, until itself life.

Thanks Platzi-teacher and Platzi-mates.

Iteration cycles

  1. Requirements: user stories (the what).
  2. Design: the how, through brainstorming or design thinking, besides the estimated times (the when (poker planning, consensus on estimations eliminating assumptions)).
  3. Code: the designed features according to the user stories planning.
  4. Test: the software created in front of the user stories).

Awesome content and methodology so far on the course! I share my notes (complementing the definitions @erwinfriasmtz has shared on the previous post):
Customer-oriented work

  1. Accurate communication of the requirements (make all the necessary questions before starting the creation of user stories).
  2. Brainstorming: ideas about the project design (get good requirements that will create great results and great software).
  3. User stories creation (short and easy to understand) to satisfy the customer through early and continuous delivery of valuable software (iterations).
  4. Estimates鈥 when those stories will be built? How long will it take to complete the project? (sum of all the estimates of the user stories).
    What if the time to complete the project exceeds customer鈥檚 expectations? Go back and re-prioritize the user stories with the customer; the customer is responsible for selecting the most relevant user stories to cut the total estimated time, and the least relevant user stories could be developed on further stages (offer different versions or milestones for the project development cycle).
Ey, debo felicitarte. Acabo de ver tu blog y es una genial forma de mostrar tu trabajo. Ojal谩 en alg煤n momento pueda hacer lo mismo. Saludos
hello

I love these reviews because they help us to consolidate all the knowledge we鈥檝e learned so far. 馃榾馃槈

.
They should be mandatory in every course.

Que interesante

thank you

Hello

Thanks

77

66

20

Awesone teacher

Yes

Hello

Iteration cycles

Requirements: user stories (the what).
Design: the how, through brainstorming or design thinking, besides the estimated times (the when (poker planning, consensus on estimations eliminating assumptions)).
Code: the designed features according to the user stories planning.
Test: the software created in front of the user stories).

Ok

Customer鈥檚 Inception: Customer鈥檚 Inception is the customer鈥檚 initial idea to get software for various purposes.

User Stories: A User Story is the representation of an individual task the Software has to do, it is composed of smaller tasks and it contains a title, a description and a priority value.

Iterations as part of a development process: A work period after which you get together with the customer, show her your work and receive feedback.

Accurate Communication: It is key to understanding Customer鈥檚 requirements and avoiding mistakes.

Idea Brainstorming: Is necessary to get good requirements that will create fantastic results.

Estimate: The time you agree with your team to finish User Stories.

Iteration cycle: Is a little work cycle that produces quality, working software.

Estimating the whole Project: Takes place when you decide the length of the complete project.

Reaching consensus in estimations: Takes place when you have agreed on the length of the estimation with the entire team, after playing planning poker. Hi everyone:

Taking the learned, and, my experience. I want to share with you something that it asked me in a technician interview. The scrum framework is a within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.

I tell you, the framework scrum in a minute. All start with product owner who is a person that prepare the product backlog. In this picture, you look at this in the beginning. The product owner collect the information of the product backlog with the stakeholders. Then, the product owner deliver the product backlog to the scrum master. The scrum master do the sprint planning for get the sprint backlog. The sprint planning is a meeting with the product owner, scrum master and the team. The planning pocker gets the estimations of every spring. That is to say, it gives the priority to every user story gave by the product owner, inside the product backlog. All days must do scrum daily for knowing the progress of the project. This meeting is just with the scrum master and the team. To the finish, it delivers a product increment in a meeting called sprint review. These iterations called sprints and finish with we complete all the user stories and deliver the complete product.

In principle, this is applied to the development software, but it can be applied in any project, until itself life.

Thanks Platzi-teacher and Platzi-mates.

Planning considering priorities: Takes place after having a meeting with the Customer and agreeing on the features that should be included in the next Iteration. It is the Customer鈥檚 decision to include certain features.

Milestone: It is a MAJOR release, when you show your Customer your working, functional Software and and you expect to get paid for it.

customer鈥檚 inception: the initial idea.
user stories: represent a task the software has todo
iterations as part of a development process: a period of work to show advance in the project at the customer
accurate communication: key for understanding the customer鈥檚 requirements
Idea Brainstorming: time to think of a lot of ideas for solving a problem or a task
estimate: time to agree with whit your team to finish the user stories

customer鈥檚 initial idea to get software for various purposes.

The first concept is the beginning of the client.
user stories
iterations as part of a development process.
brainstorm What are some recommendations and best practices? What kind of atmosphere does a brainstorming session need to be effective?
estimates
iteration cycles
estimation of the whole project

馃ぉ馃憤

graacias

For a review intention, this wasn鈥檛, a least in a short way, Carlos could repeat some of the concepts, well that鈥檚 my opinion.

Hi, so this is my review I:

Customer鈥檚 inception: It鈥檚 the beginning of an idea.
**User stories: **It鈥檚 an individual task to do. It contains three elements: Title, Description and priority value
Iteration as part of development process: because customer and team could be received feedback.
Accure communication: It鈥檚 about been in constant communication and know what are their requirements. Advice: Don鈥檛 try to avoid
Idea brainstorming: It鈥檚 when you have a meeting with the customer and all participate with ideas to create a project. Advice: Try to see what kind of software use the customer
Estimate: It鈥檚 the time to finish a user story and all the team must be agreed with it.
Iteration cycles: It鈥檚 the finish of the cycle of development, so you can have a meet with customer and receive feedback. It contains four elements: Requirements, design, code and testing.
**Estimating the whole project: **It鈥檚 the result to sum all user stories days.
**Reaching consensus in estimations: **You could be use Planning Poker
**Planning considering priorities: **When a project is too long, the customer must decide the priority of user stories
Milestones: It鈥檚 a major release.

Thank you teacher! the course so far is amazing and interesting how to know about the process to created some code-product! 馃槑馃惏

kflfi
nice

User Stories: A User Story is the representation of an individual task the Software has to do, it is composed of smaller tasks and it contains a title, a description and a priority value.