If this material is helpful, please leave a comment and support us to continue.
Table of Contents
In this context, feedback refers to input or observations about the expected outcome of a delivery – whether it’s the functionality, turnaround time, or quality. As such, one significant approach to incorporate this feedback is the use of Iterative development cycles in Scrum methodology.
Iterative development is a management approach where a large project is broken down into smaller, more manageable parts, known as iterations or sprints. Each sprint, lasting usually two to four weeks, focuses on developing a small set of features. At the end of each sprint, these features are reviewed and feedback is incorporated into the next sprint.
Iterative development allows the development team to incorporate feedback from stakeholders after each iteration, leading to improvements in the product based on actual user insight, rather than assumptions or predictions. This methodology is modelled on the principle of ‘inspect and adapt’.
At the end of each iteration, the Scrum team has a working, potentially shippable product increment. This working piece of software is presented to the stakeholders, who can test, use and evaluate the product. Feedback collected at this stage gives the team valuable insight into the expected outcome of delivery.
This feedback allows the team to understand whether they are on the right track with regards to delivering value. If the expected outcome does not meet the stakeholder’s requirements, it’s a signal to the team to change their approach, readjust their plans, or commit additional resources in their subsequent work.
For example, during an iteration, a software development team may work on a feature that allows users to upload documents. At the end of the iteration, stakeholders provide feedback that the document upload process is too slow and complicated for a non-technical user. The team takes this feedback, refines the feature, simplifying the upload process, and making it more efficient in the next sprint.
Scrum offers several built-in mechanisms – the various Scrum Artifacts that support incorporating feedback about the expected outcome. These include the Product Backlog, the Sprint Backlog, and the Increment.
The Product Backlog is a dynamic, ordered list of everything that is known to be needed in the product, and is the single source of requirements for any changes to be made to the product. Feedback may result in new entries to the Product Backlog, changes in their ordering, or refinement of Product Backlog items.
The Sprint Backlog is a set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment. Stakeholder feedback can cause adjustments to the Sprint Backlog as the team adapts to meet the expectations.
The Increment is the sum of all the Product Backlog items completed during a Sprint, which cumulatively add value to the product. Feedback about the expected outcome will reflect on the quality and suitability of the increment, and this feedback will influence the development of future increments.
In conclusion, incorporating feedback about the expected outcome of a delivery into the scrum development process not only leads to a product that meets user expectations but also fosters continuous improvement. Iterative development and effective use of Scrum artifacts are practical, hands-on approaches that Advanced Certified Scrum Developers employ to navigate the dynamic landscape of product delivery.
Answer: True
Explanation: Feedback in Scrum is a core principle that allows team members to adjust and improve their work processes and performance for better outcomes.
Answer: B) Refine and adapt the product backlog
Explanation: Scrum recommends refining and adapting the product backlog based on the feedback to improve the end product’s quality and meet clients’ expectations.
Answer: D) All stakeholders including Scrum team, Product Owner and customers
Explanation: Any stakeholder, including the Scrum team, Product Owner, and customers, can provide valuable feedback.
Answer: A) True
Explanation: Scrum reviews, or sprint reviews, are held at the end of each sprint to inspect the increment and adapt the backlog if needed. This meeting provides an opportunity to collect feedback.
Answer: B) False
Explanation: Scrum is an Agile methodology which encourages flexibility and adaptability. The expected outcomes of delivery can be updated based on feedback.
Answer: C) Sprint retrospective
Explanation: In the sprint retrospective, the Scrum team discusses what worked well, what didn’t, and ways they can improve in the next sprint, including feedback about the outcome of the delivery.
Answer: B) False
Explanation: Ignoring feedback usually leads to unsuccessful sprints and unsatisfied product owners and customers.
Answer: A) Direct and detailed
Explanation: Direct and detailed feedback helps to understand the exact expectations and make necessary adjustments to meet the desired outcome.
Answer: B) False
Explanation: Feedback should be transparent in Scrum methodology in order to make necessary improvements and adjustments.
Answer: E) All of the above
Explanation: Feedback can and should be discussed in all these meetings as it helps the Scrum team to create a product that aligns with the expectations.
42 Replies to “discuss at least one approach to incorporate feedback about the expected outcome of a delivery.”
A great approach to incorporate feedback about the expected outcome of a delivery in A-CSD is to use Acceptance Test-Driven Development (ATDD).
I’ve found ATDD particularly effective in improving communication between developers, testers, and stakeholders.
Absolutely, ATDD aligns well with Agile principles and helps in setting clear expectations from the beginning.
One of the best ways to incorporate feedback is through Sprint Reviews where stakeholders actively participate.
Sprint reviews are the cornerstone of getting valuable feedback. They ensure that the product meets user expectations.
Agreed! Sprint reviews provide a forum to capture stakeholders’ insights early.
Using Continuous Feedback Loops can significantly improve the delivery outcomes.
Yes, continuous feedback is crucial. It helps in making incremental improvements early on.
I always integrate daily feedback into my sprints; it keeps everyone on the same page.
Continuous Integration/Continuous Deployment pipelines also facilitate timely feedback.
With automated tests in the pipeline, quality feedback is continuously produced, which is extremely beneficial.
CI/CD allows for immediate feedback on code changes, ensuring quick resolution of any issues.
Really appreciate the insights shared in this post!
This blog post is really helpful. Appreciate the effort!
This information is useful for my current project. Appreciate it!
Appreciate the comprehensive information provided here. Thanks!
Another approach is to use Prototypes or MVPs to gather early feedback from stakeholders.
Creating an MVP allows you to test the core functionalities with real users before full-scale development.
Prototyping helps in validating ideas early, saving time and resources in the long run.
Constructive feedback loops with regular updates are imperative for achieving the desired delivery outcomes.
They also help in building trust with stakeholders as they see continuous progress.
Yes, regular updates and feedback loops make the development process much more adaptive and responsive.
Collaborative workshops with stakeholders are effective for aligning expectations and getting invaluable feedback.
Workshops foster a collaborative environment where stakeholders can share their concerns and suggestions openly.
They are also great for brainstorming and coming up with innovative solutions together with the stakeholders.
Great read, excited to implement these techniques in my workflow!
Not a fan of ATDD. I find it too rigid sometimes.
I can see why you’d think that. Sometimes tailoring ATDD to fit the project can make it less rigid.
Appreciate this detailed post. It’s a great read!
Thank you for sharing these strategies. Very useful!
Behavior-Driven Development (BDD) is another excellent method for incorporating feedback.
I agree! BDD ensures that the development meets the business goals, not just the technical requirements.
BDD helps in understanding the user requirements in a better way. The use of Gherkin language is a big plus!
Great post! Exactly what I was looking for.
I think involving end-users directly in the feedback process can greatly enhance the expected outcomes.
Direct user involvement ensures that the product remains user-centric, making it more likely to succeed.
True, direct feedback from end-users can highlight issues that might not be obvious to the development team.
Glad I stumbled upon this post. Very enlightening!
Thanks for this post. It was really informative!
User story mapping is an effective technique to gather feedback and set expectations.
User story mapping helps align the team’s work with the user’s needs. I’ve used it and it works wonders.
It also helps in breaking down the work in manageable pieces. A must for complex projects!