Capstone Presentation

Scenario
Your technical team is consulting for a company Cloud Dimensions. Cloud
Dimensions has selected ServiceNow to support their global organization. They
will need assistance in implementing ServiceNow based on their requirements
identified in the Statement of Work.
Objective
Using implementation best practices learned in ServiceNow Platform Implementation,
these are the objectives of this capstone:

● Practice planning and coordinating Sprints 1, 2, and 3 as a self-organizing

team
● Implement stories using skills learned in Platform Implementation and
ServiceNow Administration Fundamentals
● Use common resources, such as Docs, Now Learning, Developer, and
Community to learn about how to satisfy requirements not covered in class
● Package solutions into update sets and scoped applications for
deployment to a test platform
Group Deliverables
● Create and manage user stories to capture a description of the software
feature and capability from an end-user perspective being implemented
● ServiceNow platform demonstration of features deployed
● Deliver a business case presentation demonstrating the expected commercial
benefit of an implementation (ex. Powerpoint, Prezi, Canva etc)
● Tech and Non-tech audience
● 10 min duration (1-2 min Q&A)
Individual Deliverable
Written Reflection: All learners will submit a brief explanation of their role,
responsibilities, and contributions to their groups.
Rubric (Also attached to assignment in GC)
● Individual Written Reflection: 10%
● Cohesive Slides and Presentation Flow: 30%
● Compelling User Story: 10%
● Automation / POC (Proof of Concept) Quality: 20%
● Sales Pitch: 10%
● Time Management (10 Minutes - 8 Minutes Presentation & 2 Minutes Q&A):
10%
● Q&A Handling: 10%
What is a User Story?
A user story is a short, simple description of a feature told from the perspective of
the person who desires the new capability, usually a user or customer of the
system
Tells WHY, WHO, and WHAT
As a < type of user >, I want < some goal > so that < some reason >.
Capstone Collaborative Roles and Responsibilities
Below are suggested group roles. We encourage you to develop your group roles
based on the tasks you feel will be critical to your group’s success. Established
roles should guide your group's work but not limit how you support each other.

For example, all group members are expected to contribute their ideas and time,
no matter what role they have in their group.
Examples of Collaborative Roles
Presentation Designer: This person creates the group's presentation ensuring all components are in place and the
design is cohesive

Manager: Manages the group by helping to ensure that the group stays on task, is focused, and has room for
everyone in the conversation.

Recorder: Keeps a record of those in the group and the roles they play in the group. The recorder also records critical
points from the small group’s discussion and findings or answers.

Presenter: Presents the presentation. The Spokesperson should rely on the recorder’s notes to guide their report.

Strategy Analyst: Observes team dynamics and guides the consensus-building process (helps group members come
to a common conclusion).
Conflict Resolution
Unavoidable conflicts often arise when you work on team projects. Coworker’s
differences can contrast sharply to your own, creating tension within the group.
These differences are not necessarily a bad thing, though. Healthy constructive
criticism helps create diverse methods of thinking and solutions to difficult
problems.
There are many responses to conflict within a team, including ignoring the issue,
responding with passive aggressive actions, or even blaming the other people
involved. Obvious errors usually only appear in retrospect, but here are a few tips
for recognizing and solving conflict when working in a group.
1. Acknowledge the Conflict
Ignoring the issues may save someone’s feelings in the short run, but more than
likely you will work with this person on future projects. If the issues continue to
arise, your built-up resentment may eventually lead to arguments. Avoid anger
buildups by facing the conflict head-on and letting your teammate know you
disagree with their course of action. While not always pleasant, getting these small
disagreements out in the open can help head off future disputes.
2. Stop and Cool Off
Take a minute to think through the course of action you would like to pursue. Avoid
destructive behaviors like:

● Pointing fingers
● Insults
● Ultimatums and rigid demands
● Defensive attitudes
● Complaining behind teammates backs
● Making assumptions about others behaviors
3. Clarify Positions
Let everyone voice his or her opinions on the conflict and be heard. Allowing each
team member to explain and elucidate his or her stance will prevent
miscommunication. Plus, allowing them to rationalize their opinions may bring
more agreement and understanding from other team members.

While people are explaining their viewpoints on the issue in question, practice
active listening. Pay attention and refrain from jumping to conclusions.
4. List Facts and Assumptions Based on Each Position
Once each team member has been allowed to explain their stance on the conflict,
list out the facts and assumptions that have been made. Simply writing down the
complex facets of an argument can make things appear much clearer to the team.
If one side of the conflict is lacking in reasoning, it may be obvious during this
step. However, examining the information as a group prevents irrational
arguments or possible favoritism from team members.