Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Development Tools

To View or Not to View (back-end Service API completed work)

Since the Sprint Review focuses on demonstrating to the PO, stakeholders, others, completed working software, it would suggest this goal would lean towards front-end UI facing functionality that can be seen and easily understood by the non-technical team members (the PO and stakeholders). Does it make sense and is it a valuable use of time to include demoing back-end Service API functionality to the non-technical team members? While I think it important to convey the message to PO/stakeholders that the Service engineers did made progress and deliver working software, if the information or demonstration is "technical" in nature that does not fully make sense to the Business team members, does it still provide value with respect to this Scrum event?

2 Answers

Steven Parker
Steven Parker
229,982 Points

Since a back-end service functionality most likely implements a capability used by the front-end, in most cases it should be possible to demonstrate the new features using the front end. If that's not possible (for example, if the new code only enhances security), then it might make sense to substitute an explanatory presentation for the demonstration.

Thank you for the reply Steven. In some cases it is not possible to demo delivered service functionality from a user facing perspective when it is very early on in a project because the UI is not yet integrated with these early stage service deliverables (the UI component/s with the dependency on the delivered Service User Story may not be built yet and planned for a later sprint). So while we could still have the Service Engineer bring up his delivered service User Story and even demo something "technical", I was curious whether this is viewed as valuable use of time or the norm within "scrum" methodology given this may not provide a lot of value to demo for Business stakeholders or the Product Owner/s.

I like the alternative idea of at least providing an explanatory presentation.

Thanks again, your reply was much appreciated.