“Agile itself is just a newer, best-of-breed collection of methodologies used to develop and maintain software” (Ambler & Holitza, 2012). Behind all of the great processes within the agile framework, none of it is possible without the people to organize it and execute it. The agile team consists of six primary roles and five secondary roles. Similar to other methodologies, agile allows one person to hold one or more roles. For example, a person can be in the role of the team member while also filing the role of the team leader. We will cover the primary roles, what the agile team is, what the backlog is, what they are for and how they are important.
The first role is the most important, the stakeholder. Without them, there is no agile team because the stakeholder is the one requesting the work to be done in the first place. They are normally not just an end-user; they may also be the one with the money. The second role is the product owner. The product owner is the liaison between the agile team members and the stakeholder. The product owner is what is known as the “one voice of the customer” (Ambler & Holitza, 2012). The product owner is also responsible for sustaining and ranking items in the backlog which will be discussed later. The third role is the regular team member. The team member is the one doing the work. The role of the team member can refer to anyone from the people writing the code to the people running the tests.
Furthermore, the fourth role is the team leader. In addition to wearing their programming hat, one of the team members also has to lead the team to successful completion. The team leader is mainly there to keep everyone focused and on task. For example, to help the team stay focused the team leader will resolve issues before the issues jeopardize the sprint deliverables in order to let the team members continue working towards their goal for the day. The fifth role to mention is the architecture owner. The architecture owner is someone who owns the architecture of the solution. In a small team you could have multiple architecture owners or have everyone fill the role. On the other hand, having many architecture owners within a large team would be problematic. It is often difficult to make design decisions by committee. Instead, in a large team, there should only be or a select few satisfying the role of the architecture owner. The last and final role to mention is the agile mentor. The agile mentor is not necessarily part of the agile team but they are influential. The agile mentor is basically a coach and nothing more. They are usually well versed in the techniques of the agile framework and their whole purpose is to provide feedback and recommendations to make the teams more successful in their agile implementation.
So how does the agile team decide what gets worked on? That is where the concept of a backlog comes into play. The backlog is basically a list of requirements and there are multiple backlogs within one particular solution. They are referred to as the product backlog and a sprint backlog. Expanding on the role of the product owner, they are responsible for prioritizing and maintaining the backlogs. The product backlog contains the list of requirements for the entire product, hence the name product backlog. Moreover, the sprint backlog a subset of the requirements will be or were worked on during an iteration.
The backlogs are reviewed and/or modified during the iteration review or the release planning session. The iteration review takes place after every sprint where the team members showcase their accomplishments to the stakeholders and the product owner. In addition, if new items emerge from the iteration reviews, the product owner must take note of them so the new items can be brought to the release planning session. The release planning session consists of the same cast of characters minus the team members. The beauty of how the backlog gets maintained shows that there is no need to have a complete list of requirements on day one because this iterative process will force the backlog to become comprehensive over time. To compliment an efficient team structure would be a concise and visible backlog. It will promote innovative collaboration and integrate lessons learned from sprint to sprint. It will also allow the backlog to response to change. After every sprint all of the most important items get moved to the top, ensuring the customer is continually getting what they desire the most. “In practice, it's not unusual to see a team select, for example, the top five items and then two items from lower on the list that are associated with the initial five” (Software, 2014).
References
Ambler, S. W., & Holitza, M. (2012). Agile For Dummies IBM Limited Edition. Hoboken: John Wiley & Sons, Inc.
Software, M. G. (2014, 7 13). Mountain Goat Software. Retrieved from Topics in Scrum: http://www.mountaingoatsoftware.com/agile/scrum/product-backlog

“Agile itself is just a newer, best-of-breed collection of methodologies used to develop and maintain software” (Ambler & Holitza, 2012).¹ Behind all of the great processes within the agile framework, none of it is possible without the people to organize it and execute it.¹ The agile team consists of six primary roles and five secondary roles.¹ Similar to other methodologies, agile allows one person to hold one or more roles.¹ For example, a person can be in the role of the team member while also filing the role of the team leader.¹ We will cover the primary roles, what the agile team is, what the backlog is, what they are for and how they are important.
The first role is the most important, the stakeholder. Without them, there is no agile team because the stakeholder is the one requesting the work to be done in the first place. They are normally not just an end-user; they may also be the one with the money. The second role is the product owner. The product owner is the liaison between the agile team members and the stakeholder. The product owner is what is known as the “one voice of the customer” (Ambler & Holitza, 2012). The product owner is also responsible for sustaining and ranking items in the backlog which will be discussed later. The third role is the regular team member. The team member is the one doing the work. The role of the team member can refer to anyone from the people writing the code to the people running the tests.
Furthermore, the fourth role is the team leader. In addition to wearing their programming hat, one of the team members also has to lead the team to successful completion. The team leader is mainly there to keep everyone focused and on task. For example, to help the team stay focused the team leader will resolve issues before the issues jeopardize the sprint deliverables in order to let the team members continue working towards their goal for the day. The fifth role to mention is the architecture owner. The architecture owner is someone who owns the architecture of the solution. In a small team you could have multiple architecture owners or have everyone fill the role. On the other hand, having many architecture owners within a large team would be problematic. It is often difficult to make design decisions by committee. Instead, in a large team, there should only be or a select few satisfying the role of the architecture owner. The last and final role to mention is the agile mentor. The agile mentor is not necessarily part of the agile team but they are influential. The agile mentor is basically a coach and nothing more. They are usually well versed in the techniques of the agile framework and their whole purpose is to provide feedback and recommendations to make the teams more successful in their agile implementation.
So how does the agile team decide what gets worked on? That is where the concept of a backlog comes into play. The backlog is basically a list of requirements and there are multiple backlogs within one particular solution. They are referred to as the product backlog and a sprint backlog. Expanding on the role of the product owner, they are responsible for prioritizing and maintaining the backlogs. The product backlog contains the list of requirements for the entire product, hence the name product backlog. Moreover, the sprint backlog a subset of the requirements will be or were worked on during an iteration.
The backlogs are reviewed and/or modified during the iteration review or the release planning session. The iteration review takes place after every sprint where the team members showcase their accomplishments to the stakeholders and the product owner. In addition, if new items emerge from the iteration reviews, the product owner must take note of them so the new items can be brought to the release planning session. The release planning session consists of the same cast of characters minus the team members. The beauty of how the backlog gets maintained shows that there is no need to have a complete list of requirements on day one because this iterative process will force the backlog to become comprehensive over time. To compliment an efficient team structure would be a concise and visible backlog. It will promote innovative collaboration and integrate lessons learned from sprint to sprint. It will also allow the backlog to response to change. After every sprint all of the most important items get moved to the top, ensuring the customer is continually getting what they desire the most. “In practice, it's not unusual to see a team select, for example, the top five items and then two items from lower on the list that are associated with the initial five” (Software, 2014).
References
Ambler, S. W., & Holitza, M. (2012). Agile For Dummies IBM Limited Edition. Hoboken: John Wiley & Sons, Inc.
Software, M. G. (2014, 7 13). Mountain Goat Software. Retrieved from Topics in Scrum: http://www.mountaingoatsoftware.com/agile/scrum/product-backlog

¹Is this part of the essay your introduction? In your introduction, you should capture the reader's interest, provide background information about your topic, and present your thesis sentence. Look in the Writer's Handbook for ways to improve your introduction.

“Agile itself is just a newer, best-of-breed collection of methodologies used to develop and maintain software” (Ambler & Holitza, 2012). Behind all of the great processes within the agile framework, none of it is possible without the people to organize it and execute it. The agile team consists of six primary roles and five secondary roles. Similar to other methodologies, agile allows one person to hold one or more roles. For example, a person can be in the role of the team member while also filing the role of the team leader. We will cover the primary roles, what the agile team is, what the backlog is, what they are for and how they are important.
¹ The first role is the most important, the stakeholder. Without them, there is no agile team because the stakeholder is the one requesting the work to be done in the first place. They are normally not just an end-user; they may also be the one with the money. The second role is the product owner. The product owner is the liaison between the agile team members and the stakeholder. The product owner is what is known as the “one voice of the customer” (Ambler & Holitza, 2012). The product owner is also responsible for sustaining and ranking items in the backlog which will be discussed later. The third role is the regular team member. The team member is the one doing the work. The role of the team member can refer to anyone from the people writing the code to the people running the tests.
Furthermore, the fourth role is the team leader. In addition to wearing their programming hat, one of the team members also has to lead the team to successful completion. The team leader is mainly there to keep everyone focused and on task. For example, to help the team stay focused the team leader will resolve issues before the issues jeopardize the sprint deliverables in order to let the team members continue working towards their goal for the day. The fifth role to mention is the architecture owner. The architecture owner is someone who owns the architecture of the solution. In a small team you could have multiple architecture owners or have everyone fill the role. On the other hand, having many architecture owners within a large team would be problematic. It is often difficult to make design decisions by committee. Instead, in a large team, there should only be or a select few satisfying the role of the architecture owner. The last and final role to mention is the agile mentor. The agile mentor is not necessarily part of the agile team but they are influential. The agile mentor is basically a coach and nothing more. They are usually well versed in the techniques of the agile framework and their whole purpose is to provide feedback and recommendations to make the teams more successful in their agile implementation.
So how does the agile team decide what gets worked on? That is where the concept of a backlog comes into play. The backlog is basically a list of requirements and there are multiple backlogs within one particular solution. They are referred to as the product backlog and a sprint backlog. Expanding on the role of the product owner, they are responsible for prioritizing and maintaining the backlogs. The product backlog contains the list of requirements for the entire product, hence the name product backlog. Moreover, the sprint backlog a subset of the requirements will be or were worked on during an iteration.
The backlogs are reviewed and/or modified during the iteration review or the release planning session. The iteration review takes place after every sprint where the team members showcase their accomplishments to the stakeholders and the product owner. In addition, if new items emerge from the iteration reviews, the product owner must take note of them so the new items can be brought to the release planning session. The release planning session consists of the same cast of characters minus the team members. The beauty of how the backlog gets maintained shows that there is no need to have a complete list of requirements on day one because this iterative process will force the backlog to become comprehensive over time. To compliment an efficient team structure would be a concise and visible backlog. It will promote innovative collaboration and integrate lessons learned from sprint to sprint. It will also allow the backlog to response to change. After every sprint all of the most important items get moved to the top, ensuring the customer is continually getting what they desire the most. “In practice, it's not unusual to see a team select, for example, the top five items and then two items from lower on the list that are associated with the initial five” (Software, 2014).
References
Ambler, S. W., & Holitza, M. (2012). Agile For Dummies IBM Limited Edition. Hoboken: John Wiley & Sons, Inc.
Software, M. G. (2014, 7 13). Mountain Goat Software. Retrieved from Topics in Scrum: http://www.mountaingoatsoftware.com/agile/scrum/product-backlog

¹Is this sentence really a part of your thesis? Remember that a thesis controls the whole content of your essay. You need to strengthen this thesis so that you clearly state the main point you will be making. Look in the Writer's Handbook for tips on doing this.

“Agile itself is just a newer, best-of-breed collection of methodologies used to develop and maintain software” (Ambler & Holitza, 2012). Behind all of the great processes within the agile framework, none of it is possible without the people to organize it and execute it. The agile team consists of six primary roles and five secondary roles. Similar to other methodologies, agile allows one person to hold one or more roles. For example, a person can be in the role of the team member while also filing the role of the team leader. We will cover the primary roles, what the agile team is, what the backlog is, what they are for and how they are important.
The first role is the most important, the stakeholder.¹ Without them, there is no agile team because the stakeholder is the one requesting the work to be done in the first place. They are normally not just an end-user; they may also be the one with the money. The second role is the product owner. The product owner is the liaison between the agile team members and the stakeholder. The product owner is what is known as the “one voice of the customer” (Ambler & Holitza, 2012). The product owner is also responsible for sustaining and ranking items in the backlog which will be discussed later. The third role is the regular team member. The team member is the one doing the work. The role of the team member can refer to anyone from the people writing the code to the people running the tests.
Furthermore, the fourth role is the team leader.¹ In addition to wearing their programming hat, one of the team members also has to lead the team to successful completion. The team leader is mainly there to keep everyone focused and on task. For example, to help the team stay focused the team leader will resolve issues before the issues jeopardize the sprint deliverables in order to let the team members continue working towards their goal for the day. The fifth role to mention is the architecture owner. The architecture owner is someone who owns the architecture of the solution. In a small team you could have multiple architecture owners or have everyone fill the role. On the other hand, having many architecture owners within a large team would be problematic. It is often difficult to make design decisions by committee. Instead, in a large team, there should only be or a select few satisfying the role of the architecture owner. The last and final role to mention is the agile mentor. The agile mentor is not necessarily part of the agile team but they are influential. The agile mentor is basically a coach and nothing more. They are usually well versed in the techniques of the agile framework and their whole purpose is to provide feedback and recommendations to make the teams more successful in their agile implementation.
So how does the agile team decide what gets worked on?¹ That is where the concept of a backlog comes into play. The backlog is basically a list of requirements and there are multiple backlogs within one particular solution. They are referred to as the product backlog and a sprint backlog. Expanding on the role of the product owner, they are responsible for prioritizing and maintaining the backlogs. The product backlog contains the list of requirements for the entire product, hence the name product backlog. Moreover, the sprint backlog a subset of the requirements will be or were worked on during an iteration.
The backlogs are reviewed and/or modified during the iteration review or the release planning session. The iteration review takes place after every sprint where the team members showcase their accomplishments to the stakeholders and the product owner. In addition, if new items emerge from the iteration reviews, the product owner must take note of them so the new items can be brought to the release planning session. The release planning session consists of the same cast of characters minus the team members. The beauty of how the backlog gets maintained shows that there is no need to have a complete list of requirements on day one because this iterative process will force the backlog to become comprehensive over time. To compliment an efficient team structure would be a concise and visible backlog. It will promote innovative collaboration and integrate lessons learned from sprint to sprint. It will also allow the backlog to response to change. After every sprint all of the most important items get moved to the top, ensuring the customer is continually getting what they desire the most. “In practice, it's not unusual to see a team select, for example, the top five items and then two items from lower on the list that are associated with the initial five” (Software, 2014).
References
Ambler, S. W., & Holitza, M. (2012). Agile For Dummies IBM Limited Edition. Hoboken: John Wiley & Sons, Inc.
Software, M. G. (2014, 7 13). Mountain Goat Software. Retrieved from Topics in Scrum: http://www.mountaingoatsoftware.com/agile/scrum/product-backlog

¹Criterion has identified three or more main ideas in your essay. Do these ideas support the thesis statement of your essay? Do you use examples, explanations, and details to support and extend your main ideas? Does everything connect back to your thesis statement? Look in the Writer's Handbook for ways to develop main ideas.

“Agile itself is just a newer, best-of-breed collection of methodologies used to develop and maintain software” (Ambler & Holitza, 2012). Behind all of the great processes within the agile framework, none of it is possible without the people to organize it and execute it. The agile team consists of six primary roles and five secondary roles. Similar to other methodologies, agile allows one person to hold one or more roles. For example, a person can be in the role of the team member while also filing the role of the team leader. We will cover the primary roles, what the agile team is, what the backlog is, what they are for and how they are important.
The first role is the most important, the stakeholder. Without them, there is no agile team because the stakeholder is the one requesting the work to be done in the first place.¹ They are normally not just an end-user; they may also be the one with the money.¹ The second role is the product owner.¹ The product owner is the liaison between the agile team members and the stakeholder.¹ The product owner is what is known as the “one voice of the customer” (Ambler & Holitza, 2012).¹ The product owner is also responsible for sustaining and ranking items in the backlog which will be discussed later.¹ The third role is the regular team member.¹ The team member is the one doing the work.¹ The role of the team member can refer to anyone from the people writing the code to the people running the tests.¹
Furthermore, the fourth role is the team leader. In addition to wearing their programming hat, one of the team members also has to lead the team to successful completion.¹ The team leader is mainly there to keep everyone focused and on task.¹ For example, to help the team stay focused the team leader will resolve issues before the issues jeopardize the sprint deliverables in order to let the team members continue working towards their goal for the day.¹ The fifth role to mention is the architecture owner.¹ The architecture owner is someone who owns the architecture of the solution.¹ In a small team you could have multiple architecture owners or have everyone fill the role.¹ On the other hand, having many architecture owners within a large team would be problematic.¹ It is often difficult to make design decisions by committee.¹ Instead, in a large team, there should only be or a select few satisfying the role of the architecture owner.¹ The last and final role to mention is the agile mentor.¹ The agile mentor is not necessarily part of the agile team but they are influential.¹ The agile mentor is basically a coach and nothing more.¹ They are usually well versed in the techniques of the agile framework and their whole purpose is to provide feedback and recommendations to make the teams more successful in their agile implementation.
¹ So how does the agile team decide what gets worked on? That is where the concept of a backlog comes into play.¹ The backlog is basically a list of requirements and there are multiple backlogs within one particular solution.¹ They are referred to as the product backlog and a sprint backlog.¹ Expanding on the role of the product owner, they are responsible for prioritizing and maintaining the backlogs.¹ The product backlog contains the list of requirements for the entire product, hence the name product backlog.¹ Moreover, the sprint backlog a subset of the requirements will be or were worked on during an iteration.¹
The backlogs are reviewed and/or modified during the iteration review or the release planning session. The iteration review takes place after every sprint where the team members showcase their accomplishments to the stakeholders and the product owner. In addition, if new items emerge from the iteration reviews, the product owner must take note of them so the new items can be brought to the release planning session. The release planning session consists of the same cast of characters minus the team members. The beauty of how the backlog gets maintained shows that there is no need to have a complete list of requirements on day one because this iterative process will force the backlog to become comprehensive over time. To compliment an efficient team structure would be a concise and visible backlog. It will promote innovative collaboration and integrate lessons learned from sprint to sprint. It will also allow the backlog to response to change. After every sprint all of the most important items get moved to the top, ensuring the customer is continually getting what they desire the most. “In practice, it's not unusual to see a team select, for example, the top five items and then two items from lower on the list that are associated with the initial five” (Software, 2014).
References
Ambler, S. W., & Holitza, M. (2012). Agile For Dummies IBM Limited Edition. Hoboken: John Wiley & Sons, Inc.
Software, M. G. (2014, 7 13). Mountain Goat Software. Retrieved from Topics in Scrum: http://www.mountaingoatsoftware.com/agile/scrum/product-backlog

¹Criterion has identified three or more supporting ideas in this paragraph. Do these ideas support the topic sentence of your paragraph? Use examples, explanations, and details to support and extend your main ideas. Look in the Writer's Handbook for ways to develop supporting ideas.

“Agile itself is just a newer, best-of-breed collection of methodologies used to develop and maintain software” (Ambler & Holitza, 2012). Behind all of the great processes within the agile framework, none of it is possible without the people to organize it and execute it. The agile team consists of six primary roles and five secondary roles. Similar to other methodologies, agile allows one person to hold one or more roles. For example, a person can be in the role of the team member while also filing the role of the team leader. We will cover the primary roles, what the agile team is, what the backlog is, what they are for and how they are important.
The first role is the most important, the stakeholder. Without them, there is no agile team because the stakeholder is the one requesting the work to be done in the first place. They are normally not just an end-user; they may also be the one with the money. The second role is the product owner. The product owner is the liaison between the agile team members and the stakeholder. The product owner is what is known as the “one voice of the customer” (Ambler & Holitza, 2012). The product owner is also responsible for sustaining and ranking items in the backlog which will be discussed later. The third role is the regular team member. The team member is the one doing the work. The role of the team member can refer to anyone from the people writing the code to the people running the tests.
Furthermore, the fourth role is the team leader. In addition to wearing their programming hat, one of the team members also has to lead the team to successful completion. The team leader is mainly there to keep everyone focused and on task. For example, to help the team stay focused the team leader will resolve issues before the issues jeopardize the sprint deliverables in order to let the team members continue working towards their goal for the day. The fifth role to mention is the architecture owner. The architecture owner is someone who owns the architecture of the solution. In a small team you could have multiple architecture owners or have everyone fill the role. On the other hand, having many architecture owners within a large team would be problematic. It is often difficult to make design decisions by committee. Instead, in a large team, there should only be or a select few satisfying the role of the architecture owner. The last and final role to mention is the agile mentor. The agile mentor is not necessarily part of the agile team but they are influential. The agile mentor is basically a coach and nothing more. They are usually well versed in the techniques of the agile framework and their whole purpose is to provide feedback and recommendations to make the teams more successful in their agile implementation.
So how does the agile team decide what gets worked on? That is where the concept of a backlog comes into play. The backlog is basically a list of requirements and there are multiple backlogs within one particular solution. They are referred to as the product backlog and a sprint backlog. Expanding on the role of the product owner, they are responsible for prioritizing and maintaining the backlogs. The product backlog contains the list of requirements for the entire product, hence the name product backlog. Moreover, the sprint backlog a subset of the requirements will be or were worked on during an iteration.
The backlogs are reviewed and/or modified during the iteration review or the release planning session.¹ The iteration review takes place after every sprint where the team members showcase their accomplishments to the stakeholders and the product owner.¹ In addition, if new items emerge from the iteration reviews, the product owner must take note of them so the new items can be brought to the release planning session.¹ The release planning session consists of the same cast of characters minus the team members.¹ The beauty of how the backlog gets maintained shows that there is no need to have a complete list of requirements on day one because this iterative process will force the backlog to become comprehensive over time.¹ To compliment an efficient team structure would be a concise and visible backlog.¹ It will promote innovative collaboration and integrate lessons learned from sprint to sprint.¹ It will also allow the backlog to response to change.¹ After every sprint all of the most important items get moved to the top, ensuring the customer is continually getting what they desire the most.¹ “In practice, it's not unusual to see a team select, for example, the top five items and then two items from lower on the list that are associated with the initial five” (Software, 2014).
¹ References
Ambler, S. W., & Holitza, M. (2012). Agile For Dummies IBM Limited Edition. Hoboken: John Wiley & Sons, Inc.
Software, M. G. (2014, 7 13). Mountain Goat Software. Retrieved from Topics in Scrum: http://www.mountaingoatsoftware.com/agile/scrum/product-backlog

¹Is this part of the essay your conclusion? A conclusion reminds the reader about your thesis, stresses the importance of the ideas you have developed, and leaves the reader with thought-provoking ideas. The Writer's Handbook can provide ideas for improving your conclusion.

“Agile itself is just a newer, best-of-breed collection of methodologies used to develop and maintain software” (Ambler & Holitza, 2012). Behind all of the great processes within the agile framework, none of it is possible without the people to organize it and execute it. The agile team consists of six primary roles and five secondary roles. Similar to other methodologies, agile allows one person to hold one or more roles. For example¹, a person can be in the role of the team member while also filing the role of the team leader. We will cover the primary roles, what the agile team is, what the backlog is, what they are for and how they are important.
The first role is the most important, the stakeholder. Without them, there is no agile team because the stakeholder is the one requesting the work to be done in the first place. They are normally not just an end-user; they may also be the one with the money. The second role is the product owner. The product owner is the liaison between the agile team members and the stakeholder. The product owner is what is known as the “one voice of the customer” (Ambler & Holitza, 2012). The product owner is also responsible for sustaining and ranking items in the backlog which will be discussed later. The third role is the regular team member. The team member is the one doing the work. The role of the team member can refer to anyone from the people writing the code to the people running the tests.
Furthermore¹, the fourth role is the team leader. In addition to¹ wearing their programming hat, one of the team members also has to lead the team to successful completion. The team leader is mainly there to keep everyone focused and on task. For example¹, to help the team stay focused the team leader will resolve issues before the issues jeopardize the sprint deliverables in order to let the team members continue working towards their goal for the day. The fifth role to mention is the architecture owner. The architecture owner is someone who owns the architecture of the solution. In a small team you could have multiple architecture owners or have everyone fill the role. On the other hand¹, having many architecture owners within a large team would be problematic. It is often difficult to make design decisions by committee. Instead¹, in a large team, there should only be or a select few satisfying the role of the architecture owner. The last and final role to mention is the agile mentor. The agile mentor is not necessarily part of the agile team but they are influential. The agile mentor is basically a coach and nothing more. They are usually well versed in the techniques of the agile framework and their whole purpose is to provide feedback and recommendations to make the teams more successful in their agile implementation.
So¹ how does the agile team decide what gets worked on? That is where the concept of a backlog comes into play. The backlog is basically a list of requirements and there are multiple backlogs within one particular solution. They are referred to as the product backlog and a sprint backlog. Expanding on the role of the product owner, they are responsible for prioritizing and maintaining the backlogs. The product backlog contains the list of requirements for the entire product, hence the name product backlog. Moreover¹, the sprint backlog a subset of the requirements will be or were worked on during an iteration.
The backlogs are reviewed and/or modified during the iteration review or the release planning session. The iteration review takes place after every sprint where the team members showcase their accomplishments to the stakeholders and the product owner. In addition¹, if new items emerge from the iteration reviews, the product owner must take note of them so¹ the new items can be brought to the release planning session. The release planning session consists of the same cast of characters minus the team members. The beauty of how the backlog gets maintained shows that there is no need to have a complete list of requirements on day one because this iterative process will force the backlog to become comprehensive over time. To compliment an efficient team structure would be a concise and visible backlog. It will promote innovative collaboration and integrate lessons learned from sprint to sprint. It will also allow the backlog to response to change. After¹ every sprint all of the most important items get moved to the top, ensuring the customer is continually getting what they desire the most. “In practice, it's not unusual to see a team select, for example¹, the top five items and then two items from lower on the list that are associated with the initial five” (Software, 2014).
References
Ambler, S. W., & Holitza, M. (2012). Agile For Dummies IBM Limited Edition. Hoboken: John Wiley & Sons, Inc.
Software, M. G. (2014, 7 13). Mountain Goat Software. Retrieved from Topics in Scrum: http://www.mountaingoatsoftware.com/agile/scrum/product-backlog

¹These are the transition words and phrases you have used in your essay. Check the Writer's Handbook to see if you have used each word or phrase correctly.

“Agile itself is just a newer, best-of-breed collection of methodologies used to develop and maintain software” (Ambler & Holitza, 2012). Behind all of the great processes within the agile framework, none of it is possible without the people to organize it and execute it. The agile team consists of six primary roles and five secondary roles. Similar to other methodologies, agile allows one person to hold one or more roles. For example, a person can be in the role of the team member while also filing the role of the team leader. We will cover the primary roles, what the agile team is, what the backlog is, what they are for and how they are important.
The first role is the most important, the stakeholder. Without them, there is no agile team because the stakeholder is the one requesting the work to be done in the first place. They are normally not just an end-user; they may also be the one with the money. The second role is the product owner. The product owner is the liaison between the agile team members and the stakeholder. The product owner is what is known as the “one voice of the customer” (Ambler & Holitza, 2012). The product owner is also responsible for sustaining and ranking items in the backlog which will be discussed later. The third role is the regular team member. The team member is the one doing the work. The role of the team member can refer to anyone from the people writing the code to the people running the tests.
Furthermore, the fourth role is the team leader. In addition to wearing their programming hat, one of the team members also has to lead the team to successful completion. The team leader is mainly there to keep everyone focused and on task. For example, to help the team stay focused the team leader will resolve issues before the issues jeopardize the sprint deliverables in order to let the team members continue working towards their goal for the day. The fifth role to mention is the architecture owner. The architecture owner is someone who owns the architecture of the solution. In a small team you could have multiple architecture owners or have everyone fill the role. On the other hand, having many architecture owners within a large team would be problematic. It is often difficult to make design decisions by committee. Instead, in a large team, there should only be or a select few satisfying the role of the architecture owner. The last and final role to mention is the agile mentor. The agile mentor is not necessarily part of the agile team but they are influential. The agile mentor is basically a coach and nothing more. They are usually well versed in the techniques of the agile framework and their whole purpose is to provide feedback and recommendations to make the teams more successful in their agile implementation.
So how does the agile team decide what gets worked on? That is where the concept of a backlog comes into play. The backlog is basically a list of requirements and there are multiple backlogs within one particular solution. They are referred to as the product backlog and a sprint backlog. Expanding on the role of the product owner, they are responsible for prioritizing and maintaining the backlogs. The product backlog contains the list of requirements for the entire product, hence the name product backlog. Moreover, the sprint backlog a subset of the requirements will be or were worked on during an iteration.
The backlogs are reviewed and/or modified during the iteration review or the release planning session. The iteration review takes place after every sprint where the team members showcase their accomplishments to the stakeholders and the product owner. In addition, if new items emerge from the iteration reviews, the product owner must take note of them so the new items can be brought to the release planning session. The release planning session consists of the same cast of characters minus the team members. The beauty of how the backlog gets maintained shows that there is no need to have a complete list of requirements on day one because this iterative process will force the backlog to become comprehensive over time. To compliment an efficient team structure would be a concise and visible backlog. It will promote innovative collaboration and integrate lessons learned from sprint to sprint. It will also allow the backlog to response to change. After every sprint all of the most important items get moved to the top, ensuring the customer is continually getting what they desire the most. “In practice, it's not unusual to see a team select, for example, the top five items and then two items from lower on the list that are associated with the initial five” (Software, 2014).
References
Ambler, S. W., & Holitza, M. (2012).¹ Agile For Dummies IBM Limited Edition.¹ Hoboken: John Wiley & Sons, Inc.
¹ Software, M. G. (2014, 7 13).¹ Mountain Goat Software.¹ Retrieved from Topics in Scrum: http://www.mountaingoatsoftware.com/agile/scrum/product-backlog

¹Is this material a title, class name, section number, opening, closing, signature, or name? This material does not seem to be part of your essay.

“Agile itself is just a newer, best-of-breed collection of methodologies used to develop and maintain software” (Ambler & Holitza, 2012). Behind all of the great processes within the agile framework, none of it is possible without the people to organize it and execute it. The agile team consists of six primary roles and five secondary roles. Similar to other methodologies, agile allows one person to hold one or more roles. For example, a person can be in the role of the team member while also filing the role of the team leader. We will cover the primary roles, what the agile team is, what the backlog is, what they are for and how they are important.
The first role is the most important, the stakeholder. Without them, there is no agile team because the stakeholder is the one requesting the work to be done in the first place. They are normally not just an end-user; they may also be the one with the money. The second role is the product owner. The product owner is the liaison between the agile team members and the stakeholder. The product owner is what is known as the “one voice of the customer” (Ambler & Holitza, 2012). The product owner is also responsible for sustaining and ranking items in the backlog which will be discussed later. The third role is the regular team member. The team member is the one doing the work. The role of the team member can refer to anyone from the people writing the code to the people running the tests.
Furthermore, the fourth role is the team leader. In addition to wearing their programming hat, one of the team members also has to lead the team to successful completion. The team leader is mainly there to keep everyone focused and on task. For example, to help the team stay focused the team leader will resolve issues before the issues jeopardize the sprint deliverables in order to let the team members continue working towards their goal for the day. The fifth role to mention is the architecture owner. The architecture owner is someone who owns the architecture of the solution. In a small team you could have multiple architecture owners or have everyone fill the role. On the other hand, having many architecture owners within a large team would be problematic. It is often difficult to make design decisions by committee. Instead, in a large team, there should only be or a select few satisfying the role of the architecture owner. The last and final role to mention is the agile mentor. The agile mentor is not necessarily part of the agile team but they are influential. The agile mentor is basically a coach and nothing more. They are usually well versed in the techniques of the agile framework and their whole purpose is to provide feedback and recommendations to make the teams more successful in their agile implementation.
So how does the agile team decide what gets worked on? That is where the concept of a backlog comes into play. The backlog is basically a list of requirements and there are multiple backlogs within one particular solution. They are referred to as the product backlog and a sprint backlog. Expanding on the role of the product owner, they are responsible for prioritizing and maintaining the backlogs. The product backlog contains the list of requirements for the entire product, hence the name product backlog. Moreover, the sprint backlog a subset of the requirements will be or were worked on during an iteration.
The backlogs are reviewed and/or modified during the iteration review or the release planning session. The iteration review takes place after every sprint where the team members showcase their accomplishments to the stakeholders and the product owner. In addition, if new items emerge from the iteration reviews, the product owner must take note of them so the new items can be brought to the release planning session. The release planning session consists of the same cast of characters minus the team members. The beauty of how the backlog gets maintained shows that there is no need to have a complete list of requirements on day one because this iterative process will force the backlog to become comprehensive over time. To compliment an efficient team structure would be a concise and visible backlog. It will promote innovative collaboration and integrate lessons learned from sprint to sprint. It will also allow the backlog to response to change. After every sprint all of the most important items get moved to the top, ensuring the customer is continually getting what they desire the most. “In practice, it's not unusual to see a team select, for example, the top five items and then two items from lower on the list that are associated with the initial five” (Software, 2014).
References
Ambler, S. W., & Holitza, M. (2012). Agile For Dummies IBM Limited Edition.¹ Hoboken: John Wiley & Sons, Inc.
Software, M. G. (2014, 7 13). Mountain Goat Software.¹ Retrieved from Topics in Scrum: http://www.mountaingoatsoftware.com/agile/scrum/product-backlog

¹This sentence may be a fragment. Proofread the sentence to be sure that it has at least one independent clause with a complete subject and predicate.

“Agile itself is just a newer, best-of-breed collection of methodologies used to develop and maintain software” (Ambler & Holitza, 2012). Behind all of the great processes within the agile framework, none of it is possible without the people to organize it and execute it. The agile team consists of six primary roles and five secondary roles. Similar to other methodologies, agile allows one person to hold one or more roles. For example, a person can be in the role of the team member while also filing the role of the team leader. We will cover the primary roles, what the agile team is, what the backlog is, what they are for and how they are important.
The first role is the most important, the stakeholder. Without them, there is no agile team because the stakeholder is the one requesting the work to be done in the first place. They are normally not just an end-user; they may also be the one with the money. The second role is the product owner. The product owner is the liaison between the agile team members and the stakeholder. The product owner is what is known as the “one voice of the customer” (Ambler & Holitza, 2012). The product owner is also responsible for sustaining and ranking items in the backlog which will be discussed later. The third role is the regular team member. The team member is the one doing the work. The role of the team member can refer to anyone from the people writing the code to the people running the tests.
Furthermore, the fourth role is the team leader. In addition to wearing their programming hat, one of the team members also has to lead the team to successful completion. The team leader is mainly there to keep everyone focused and on task. For example, to help the team stay focused the team leader will resolve issues before the issues jeopardize the sprint deliverables in order to let the team members continue working towards their goal for the day. The fifth role to mention is the architecture owner. The architecture owner is someone who owns the architecture of the solution. In a small team you could have multiple architecture owners or have everyone fill the role. On the other hand, having many architecture owners within a large team would be problematic. It is often difficult to make design decisions by committee. Instead, in a large team, there should only be or a select few satisfying the role of the architecture owner. The last and final role to mention is the agile mentor. The agile mentor is not necessarily part of the agile team but they are influential. The agile mentor is basically a coach and nothing more. They are usually well versed in the techniques of the agile framework and their whole purpose is to provide feedback and recommendations to make the teams more successful in their agile implementation.
So how does the agile team decide what gets worked on? That is where the concept of a backlog comes into play. The backlog is basically a list of requirements and there are multiple backlogs within one particular solution. They are referred to as the product backlog and a sprint backlog. Expanding on the role of the product owner, they are responsible for prioritizing and maintaining the backlogs. The product backlog contains the list of requirements for the entire product, hence the name product backlog. Moreover, the sprint backlog a subset of the requirements will be or were worked on during an iteration.
The backlogs are reviewed and/or modified during the iteration review or the release planning session. The iteration review takes place after every sprint where the team members ¹showcase¹ their accomplishments to the stakeholders and the product owner. In addition, if new items emerge from the iteration reviews, the product owner must take note of them so the new items can be brought to the release planning session. The release planning session consists of the same cast of characters minus the team members. The beauty of how the backlog gets maintained shows that there is no need to have a complete list of requirements on day one because this iterative process will force the backlog to become comprehensive over time. To compliment an efficient team structure would be a concise and visible backlog. It will promote innovative collaboration and integrate lessons learned from sprint to sprint. It will also allow the backlog to response to change. After every sprint all of the most important items get moved to the top, ensuring the customer is continually getting what they desire the most. “In practice, it's not unusual to see a team select, for example, the top five items and then two items from lower on the list that are associated with the initial five” (Software, 2014).
References
Ambler, S. W., & Holitza, M. (2012). Agile For Dummies IBM Limited Edition. Hoboken: John Wiley & Sons, Inc.
Software, M. G. (2014, 7 13). Mountain Goat Software. Retrieved from Topics in Scrum: http://www.mountaingoatsoftware.com/agile/scrum/product-backlog

¹This part of the sentence contains a grammatical error or misspelled word that makes your meaning unclear.

“Agile itself is just a newer, best-of-breed collection of methodologies used to develop and maintain software” (Ambler & Holitza, 2012). Behind all of the great processes within the agile framework, none of it is possible without the people to organize it and execute it. The agile team consists of six primary roles and five secondary roles. Similar to other methodologies, agile allows one person to hold one or more roles. For example, a person can be in the role of the team member while also filing the role of the team leader. We will cover the¹ primary roles, what the agile team is, what the backlog is, what they are for and how they are important.
The first role is the most important, the stakeholder. Without them, there is no agile team because the stakeholder is the one requesting the work to be done in the first place. They are normally not just an end-user; they may also be the one with the money. The second role is the product owner. The product owner is the liaison between the agile team members and the stakeholder. The product owner is what is known as the “one voice of the customer” (Ambler & Holitza, 2012). The product owner is also responsible for sustaining and ranking items in the backlog which will be discussed later. The third role is the regular team member. The team member is the one doing the work. The role of the team member can refer to anyone from the people writing the code to the people running the tests.
Furthermore, the fourth role is the team leader. In addition to wearing their programming hat, one of the team members also has to lead the team to successful completion. The team leader is mainly there to keep everyone focused and on task². For example, to help the team stay focused the team leader will resolve issues before the issues jeopardize the sprint deliverables in order to let the team members continue working towards their goal for the day. The fifth role to mention is the architecture owner. The architecture owner is someone who owns the architecture of the solution. In a small team you could have multiple architecture owners or have everyone fill the role. On the other hand, having many architecture owners within a large team would be problematic. It is often difficult to make design decisions by committee³. Instead, in a large team, there should only be or a select few satisfying the role of the architecture owner. The last and final role to mention is the agile mentor. The agile mentor is not necessarily part of the agile team but they are influential. The agile mentor is basically a coach and nothing more. They are usually well versed in the techniques of the agile framework and their whole purpose is to provide feedback and recommendations to make the teams more successful in their agile implementation.
So how does the agile team decide what gets worked on? That is where the concept of a backlog comes into play. The backlog is basically a list of requirements and there are multiple backlogs within one particular solution. They are referred to as the product backlog and a sprint backlog. Expanding on the role of the product owner, they are responsible for prioritizing and maintaining the backlogs. The product backlog contains the list of requirements for the entire product, hence the name product backlog. Moreover, the sprint backlog a subset of the requirements will be or were worked on during an iteration.
The backlogs are reviewed and/or modified during the iteration review or the release planning session. The iteration review takes place after every sprint where the team members showcase their accomplishments to the stakeholders and the product owner. In addition, if new items emerge from the iteration reviews, the product owner must take note of them so the new items can be brought to the release planning session. The release planning session consists of the same cast of characters minus the team members. The beauty of how the backlog gets maintained shows that there is no need to have a complete list of requirements on day one because this iterative process will force the backlog to become comprehensive over time. To compliment an efficient team structure would be a concise and visible backlog. It will promote innovative collaboration and integrate lessons learned from sprint to sprint. It will also allow the backlog to response to change. After every sprint all of the most important items get moved to the top, ensuring the customer is continually getting what they desire the most. “In practice, it's not unusual to see a team select, for example, the top five items and then two items from lower on the list that are associated with the initial five” (Software, 2014).
References
Ambler, S. W., & Holitza, M. (2012). Agile For Dummies IBM Limited Edition. Hoboken: John Wiley & Sons, Inc.
Software, M. G. (2014, 7 13). Mountain Goat Software. Retrieved from Topics in Scrum: http://www.mountaingoatsoftware.com/agile/scrum/product-backlog

¹You may need to remove this article.
²You may need to use an article before this word. Consider using the article the.
³You may need to use an article before this word.

“Agile itself is just a newer, best-of-breed collection of methodologies used to develop and maintain software” (Ambler & Holitza¹, 2012). Behind all of the great processes within the agile framework, none of it is possible without the people to organize it and execute it. The agile team consists of six primary roles and five secondary roles. Similar to other methodologies, agile allows one person to hold one or more roles. For example, a person can be in the role of the team member while also filing the role of the team leader. We will cover the primary roles, what the agile team is, what the backlog is, what they are for and how they are important.
The first role is the most important, the stakeholder. Without them, there is no agile team because the stakeholder is the one requesting the work to be done in the first place. They are normally not just an end-user; they may also be the one with the money. The second role is the product owner. The product owner is the liaison between the agile team members and the stakeholder. The product owner is what is known as the “one voice of the customer” (Ambler & Holitza¹, 2012). The product owner is also responsible for sustaining and ranking items in the backlog which will be discussed later. The third role is the regular team member. The team member is the one doing the work. The role of the team member can refer to anyone from the people writing the code to the people running the tests.
Furthermore, the fourth role is the team leader. In addition to wearing their programming hat, one of the team members also has to lead the team to successful completion. The team leader is mainly there to keep everyone focused and on task. For example, to help the team stay focused the team leader will resolve issues before the issues jeopardize the sprint deliverables in order to let the team members continue working towards their goal for the day. The fifth role to mention is the architecture owner. The architecture owner is someone who owns the architecture of the solution. In a small team you could have multiple architecture owners or have everyone fill the role. On the other hand, having many architecture owners within a large team would be problematic. It is often difficult to make design decisions by committee. Instead, in a large team, there should only be or a select few satisfying the role of the architecture owner. The last and final role to mention is the agile mentor. The agile mentor is not necessarily part of the agile team but they are influential. The agile mentor is basically a coach and nothing more. They are usually well versed in the techniques of the agile framework and their whole purpose is to provide feedback and recommendations to make the teams more successful in their agile implementation.
So how does the agile team decide what gets worked on? That is where the concept of a backlog comes into play. The backlog is basically a list of requirements and there are multiple backlogs within one particular solution. They are referred to as the product backlog and a sprint backlog. Expanding on the role of the product owner, they are responsible for prioritizing and maintaining the backlogs. The product backlog contains the list of requirements for the entire product, hence the name product backlog. Moreover, the sprint backlog a subset of the requirements will be or were worked on during an iteration.
The backlogs are reviewed and/or modified during the iteration review or the release planning session. The iteration review takes place after every sprint where the team members showcase their accomplishments to the stakeholders and the product owner. In addition, if new items emerge from the iteration reviews, the product owner must take note of them so the new items can be brought to the release planning session. The release planning session consists of the same cast of characters minus the team members. The beauty of how the backlog gets maintained shows that there is no need to have a complete list of requirements on day one because this iterative process will force the backlog to become comprehensive over time. To compliment an efficient team structure would be a concise and visible backlog. It will promote innovative collaboration and integrate lessons learned from sprint to sprint. It will also allow the backlog to response to change. After every sprint all of the most important items get moved to the top, ensuring the customer is continually getting what they desire the most. “In practice, it's not unusual to see a team select, for example, the top five items and then two items from lower on the list that are associated with the initial five” (Software, 2014).
References
Ambler, S. W., & Holitza¹, M. (2012). Agile For Dummies IBM Limited Edition. Hoboken: John Wiley & Sons, Inc.
Software, M. G. (2014, 7 13). Mountain Goat Software. Retrieved from Topics in Scrum: http://www.mountaingoatsoftware.com/agile/scrum/product-backlog

¹This word is misspelled. Use a dictionary or spellchecker when you proofread your work.

“Agile itself is just a newer, best-of-breed collection of methodologies used to develop and maintain software” (Ambler & Holitza, 2012). Behind all of the great processes within the agile framework, none of it is possible without the people to organize it and execute it. The agile team¹ consists of six primary roles¹ and five secondary roles¹. Similar to other methodologies, agile allows one person to hold one or more roles¹. For example, a person can be in the role¹ of the team¹ member while also filing the role¹ of the team¹ leader. We will cover the primary roles¹, what the agile team¹ is, what the backlog¹ is, what they are for and how they are important.
The first role¹ is the most important, the stakeholder. Without them, there is no agile team¹ because the stakeholder is the one requesting the work to be done in the first place. They are normally not just an end-user; they may also be the one with the money. The second role¹ is the product owner. The product owner is the liaison between the agile team¹ members and the stakeholder. The product owner is what is known as the “one voice of the customer” (Ambler & Holitza, 2012). The product owner is also responsible for sustaining and ranking items in the backlog¹ which will be discussed later. The third role¹ is the regular team¹ member. The team¹ member is the one doing the work. The role¹ of the team¹ member can refer to anyone from the people writing the code to the people running the tests.
Furthermore, the fourth role¹ is the team¹ leader. In addition to wearing their programming hat, one of the team¹ members also has to lead the team¹ to successful completion. The team¹ leader is mainly there to keep everyone focused and on task. For example, to help the team¹ stay focused the team¹ leader will resolve issues before the issues jeopardize the sprint deliverables in order to let the team¹ members continue working towards their goal for the day. The fifth role¹ to mention is the architecture owner. The architecture owner is someone who owns the architecture of the solution. In a small team¹ you could have multiple architecture owners or have everyone fill the role¹. On the other hand, having many architecture owners within a large team¹ would be problematic. It is often difficult to make design decisions by committee. Instead, in a large team¹, there should only be or a select few satisfying the role¹ of the architecture owner. The last and final role¹ to mention is the agile mentor. The agile mentor is not necessarily part of the agile team¹ but they are influential. The agile mentor is basically a coach and nothing more. They are usually well versed in the techniques of the agile framework and their whole purpose is to provide feedback and recommendations to make the teams¹ more successful in their agile implementation.
So how does the agile team¹ decide what gets worked on? That is where the concept of a backlog¹ comes into play. The backlog¹ is basically a list of requirements and there are multiple backlogs¹ within one particular solution. They are referred to as the product backlog¹ and a sprint backlog¹. Expanding on the role¹ of the product owner, they are responsible for prioritizing and maintaining the backlogs¹. The product backlog¹ contains the list of requirements for the entire product, hence the name product backlog¹. Moreover, the sprint backlog¹ a subset of the requirements will be or were worked on during an iteration.
The backlogs¹ are reviewed and/or modified during the iteration review or the release planning session. The iteration review takes place after every sprint where the team¹ members showcase their accomplishments to the stakeholders and the product owner. In addition, if new items emerge from the iteration reviews, the product owner must take note of them so the new items can be brought to the release planning session. The release planning session consists of the same cast of characters minus the team¹ members. The beauty of how the backlog¹ gets maintained shows that there is no need to have a complete list of requirements on day one because this iterative process will force the backlog¹ to become comprehensive over time. To compliment an efficient team¹ structure would be a concise and visible backlog¹. It will promote innovative collaboration and integrate lessons learned from sprint to sprint. It will also allow the backlog¹ to response to change. After every sprint all of the most important items get moved to the top, ensuring the customer is continually getting what they desire the most. “In practice, it's not unusual to see a team¹ select, for example, the top five items and then two items from lower on the list that are associated with the initial five” (Software, 2014).
References
Ambler, S. W., & Holitza, M. (2012). Agile For Dummies IBM Limited Edition. Hoboken: John Wiley & Sons, Inc.
Software, M. G. (2014, 7 13). Mountain Goat Software. Retrieved from Topics in Scrum: http://www.mountaingoatsoftware.com/agile/scrum/product-backlog

¹You have repeated these words several times in your essay. Your essay will be stronger if you vary your word choice and substitute some other words instead. Ask your instructor for advice.