Review and your comments.
MGMT655 Team Charter | Company Baldwin
Team Members and contact information (University, 2018):
Name Preferred Email Phone Number Time Zone
MT
CT
ET
Purpose Statement: Anthony Dominick; Nika Patterson
The assignment is centered on an online Business Simulation named CAPSTONE
Offered by the CapSim Organization. The key point of this assignment is about managing business
operations (like R&D, Marketing, Production, Finance, HR / TQM etc.) to accomplish final success in
conditions of business performance. In this online Business Simulation, our Company (Baldwin) is
competing with five other competitors who are in the same Industry (Manufacturing Sensors). Baldwin
company is expected to use its business know-how resourcefully to become the leading manufacturer of
electronic sensors (Guide, 2014).
Nika Patterson
Through team work and dedication to the project will guarantee the growth and success of the
company that we are assigned too.
Team Values:
• Responsiveness – it is important for us to respond in a timely manner. Although the can be a
subjective value of what timely involves since we all are from different time zones, but when we
start the program it will sink-in (Edmondson, 2017).
• Respect – having mutual respect on other team members. Everyone, regardless of position,
ought to have respect (Edmondson, 2017).
• Resolved Conflict – unresolved conflict is a disease to the health of a team. If there is an issue
with the projector between team member, let us fix it so we can start and end the project with
new knowledge learned (Edmondson, 2017).
• Participation – all on the team feel they play an important role in completing the assignment.
We provide ownership of responsibilities, regardless of title. Get off the bench and get into the
game – don’t hide in the dugout, my friends, trust me this is something new to me as well and
participation in the center of getting a good grade and learning at the same time (Edmondson,
2017).
Contributive and constructive –
Team Expectations:
• Be willing to try the program (Wisconsin, n.d.)
• Help train other team member on assignment
• Be flexible on assignments (Wisconsin, n.d.)
Team Objectives: Anthony Dominick; Nika Patterson
• Being Dependable
• Respecting each other idea’s
• Share your ideas for improvements and help
• Communicate issues/changes (Wisconsin, n.d.)
• Support group / team decisions
• Be open to constructive feedback – don’t be negative or defensive (learning purpose)
• Enjoy the work and celebrate successes (Wisconsin, n.d.)
Team Meetings and Communication:
Since we are working as a virtual team, since we all live in different time zones – I’ll reach out
to all by email or phone – to keep all up to speed and hope each will do the same. Someone in the
group come up with a better means, bring it to the table. If you get stuck on what to do next reach out,
please. We also have the Group live chat as well. (University, 2018)
Team Assessment:
• Strengths – Nika’s strengths: good with powerpoint presentations and marketing / Anthony
strengths: Dependable; creatative and team player
• Weaknesses – Nika’s weaknesses: finance and simulation / Anthony’s weakness: problem
solving, finance, dislike deadlines and being out front.
• Team weakness – the different time zones; fear of not knowing or understanding the
assignment; fear of failure
Functional Roles:
COO/ Team Leader – Anthony Dominick
• Organizes team meetings facilitates team discussions, facilitates problem-solving and
collaboration, and strives for team consensus and win-win agreements (Guide, 2014). The COO
collects and compiles the Product Manager slides for the Board of Directors presentations
(Group Projects), adding a “state of the business” executive summary-type slide, a finance slide,
and, ideally, a “lessons learned” slide. Typically, the COO makes the final Finance decisions
just before simulation round close when financing needs for the company are available in the
Pro Formas (Guide, 2014).
Product Managers (VPs) – Nika Patterson, David Hagedorn, Sarah Heitzmann, Elias Munoz
• Each team member selects one sensor product to manage. There are five sensor products in
each company. If there are only five team members, then the COO also will manage a
product. The Product Managers (VPs) will make all functional decisions for their product –
R&D, Marketing, and Production (Guide, 2014). No decisions will be made for another VP’s
product without their agreement. Each VP will create at least four slides for the Board of
Directors Presentation (Group Project), including a cover slide, and one slide for each functional
area. Ample notes explaining and assessing decisions are included. The slides are submitted to
the COO and Instructor (Guide, 2014).
Product Manager(s):
• Five Sensor Products – Each Team members will manage a product
Market Segment Sensor Name Product Mgr.
Traditional Baker Nika Paterson
Low End Bead Anthony Dominick
High End Bid David Hagedorn
Performance Bold Sarah Heitzmann
Size Buddy Elias Munoz
Project Plan and Timeline:
• Group Project 1: Team Charter
• Group Project 2: Group Presentation to the Board of Directors regarding Practice Round 1
decisions and outcomes
• Group Project 3: Group Presentation to the Board of Directors regarding Competition Round
1 decisions and outcomes
• Competition Rounds 2 through 4: Continue to play to earn Stars and strive for the honor of
being in the top ten percentiles of all teams currently playing the simulation (University, 2018).
References
Edmondson, R. (2017, January 24). 7 Non-Negotiable Values for Teams I Lead. Retrieved from Team
Leadership: http://ronedmondson.com/2017/01/7-non-negotiable-values-for-teams-i-lead.html
Guide, C. T. (2014). Six Basic Strategies. Retrieved from Team Member Guide:
http://ww2.capsim.com/PDF/2014_Capstone_Team_Member_Guide.pdf
University, C. T. (2018, November 21). MGMT655 Team Charter / Company Baldwin. Retrieved from
Management Capstone (MGMT655-1804B-01):
https://studentlogin.coloradotech.edu/portal/6/pages/mainframe.aspx?contentframe=/portal/6/Pa
ges/Home.aspx
Wisconsin. (n.d.). Team Member Expectations. Retrieved from Minds: Wisconsin.edu:
https://minds.wisconsin.edu/bitstream/handle/1793/44769/Documents/PDF_FILES/Team%20M
ember%20Expectations.pdf