Instructions for Deliverable
- Review the rubric to make sure you understand the criteria for earning your grade. You can learn more about the specific skills being assessed by reviewing the links in Problem-Based Learning Resources(new tab).
- As a team, determine how you will present your test results. An optional template is this Scenario Testing Results Template(Word document).
- Each team member must choose at least one of the scenarios listed in Step 4 Scenarios for Testing(new tab). Carefully plan so that each team member is testing against a different scenario. If your team would like to include additional scenarios in this step, determine a team approach to conduct the extra testing.
- To conduct the test, read the scenario carefully. Describe how a team would use the Task Force Plan to work through the scenario. Analyze the plan for any weaknesses; does it provide the solution(s) needed? Make recommendations for improving the solutions(s) within the plan to better address the scenario.
- Present the results of your test as organized information. Provide a brief summary of the action steps needed to strengthen your solution. Clearly indicate team members’ contributions.
- One person from the team must submit the deliverable per the schedule outlined in your Team PBL Plan but no later than Workshop Five.
Task Details :
attached task force plan solution as agile methodology , in all these senarios will do some analysis and give pointers (as per template)
senario ; analysis, action item , solutions
need relate secenarios with agile methodology
need to work on Scenario #3 and Scenario #4
Scenario #3 – (impasse – Fear of Conflict)
In developing options for consideration the team reaches an impasse. One team member gets into the weeds quickly, and struggles with staying on ‘the main thing’. Although the team leans on their “Team Contract” for such situations, ultimately, they determine the Team Contract is not specific enough to provide remedy. These pauses add time to everyone’s already busy schedules and has happened more than once. The end result is a fear of conflict which inturn results in team members incapable of engaging in debates.
Scenario #4 – (VBM/Staffing)
The team is tasked to create a Task Force to address critical business issues, demonstrate virtuous leadership, and implement the VBM model in its work. The team struggles with the resource aspects of ‘how to identify candidates for the Task Force that would implement the VBM model’. The right fit is critically important – essentially the difference between success and failure. What actions can the team advance to identify these candidates and achieve the right fit, right role, right time for the success of the project?
TASK FORCE PROPOSAL – WATERFALL TO AGILE |
1 |
PBL Team 6 Workshop 4: Task Force Proposal – Waterfall to Agile
Krishna Amaravadi, Sunethra Duvvuru, Bindusree Polineni, Aishwarya Singh, and Nicholas White
BADM 703 – DBA Cohort 7, Indiana Wesleyan University
List of Contributors
Krishna Amaravadi – Executive Summary (Background and Current state), table of contents, formatting
Sunethra Duvvuru – Risk and Mitigation of task force using answering from last week assignment
Bindusree Polineni – Contribution to Executive Summary
Aishwarya Singh – Resources contribution
Nicholas White – Planned outline for PBL team for the assignment, researching, formatting, Action Plan section, formation of metrics for XYZ company, success metrics for task force, and incorporation of all content from contributors into cohesive “story”.
Table of Contents
Executive Summary 4
Background 4
Current State 5
Solution 6
Goals 6
Action Steps 7
Risks & Mitigations 7
Trust 7
Communication 8
Ways of Working 8
Team-member participation: 9
Resources 9
Terms & Definitions 10
References 11
PBL Team 6 Workshop 4: Task Force Proposal – Waterfall to Agile
Executive Summary
Background
Fictional XYZ company has recognized their software development projects have not generated their estimated value for the past 5 years. Their data suggests that 20% of projects fail to deliver software to production. Of the 80% that do deliver software, 70% of the projects to complete on time and none of the projects came in under budget. XYZ company follows a traditional waterfall model as shown in Figure 1 below:
Figure 1:
Waterfall Model
Note: This figure represents the life cycle of a waterfall model used in software development processes. From “Waterfall vs. V-Model vs. Agile: A comparative study on SDLC” Balaji, S., & Murugaiyan, M. S. (2012, International Journal of Information Technology and Business Management, p. 27).
Current State
As shown above, XYZ company’s process follows these stages step by step: Analysis, Design, Development, Testing, Implementation and Maintenance. Once the requirements are established the analysis stage begins where the requirements are analyzed. After the analysis, the system architecture and design are specified in the design stage. In the next stage the development part of the process is completed. Once the process enters the testing stage, all the components and units developed in the previous stage are tested. Once testing is complete without any bugs, the project is then deployed in the deployment stage. In the maintenance stage any issues that occur in the user end are fixed and the product is kept up to date to new updates.
In waterfall model all the project requirements are made clear before the analysis and design stages. Because the stages are fixed, changes in requirements are not implemented once out of the design stage. Every other stage of the model also begins and ends in a particular order. Each stage also has an assigned timeframe and is locked before moving toward the next stage. As an example, the analysis phase is locked before the design stage begins, and once the design is locked, development begins, and so forth (Balaji & Murugaiyan, 2012). The teams involved in other stages of the process are only involved when their stage begins. For example, the test team is only involved once the testing stage begins. Since the test team is not involved in the process from the beginning any defects that might have occurred in the earlier stages are found very late in the development process, which makes this model expensive and time consuming (Balaji & Murugaiyan, 2012).
Further research by the XYZ company found related material on the challenges of waterfall. According to McManus & Wood-Harper (2007), industry information was gathered on completions, cancellations, and project overruns of several companies using waterfall methodology. Out of 214 companies sampled, 51 (23.8%) were canceled, 163 were completed (76.2%). Based on the research the reason for cancellations and project overruns were due to management decisions and poor communication when it comes to finalizing proper business requirements. Even though the success rate was 76.2 %, many of the projects were behind schedule and over budget. For example, one of the companies that was 20 weeks late and 56% over budget was still considered successful only due to completion (2007).
Solution
XYZ company has decided to replace their waterfall development methodology with an agile one. To do this effectively, they have created a task force to support the implementation of agile for their software development processes. More specifically, as they work with multiple teams and dependencies, their goal is to implement SAFe, a scaled agile framework for managing multiple agile development teams (Scaled Agile, 2022).
Goals
The task force has proposed that XYZ company start with a small implementation with the task force acting as a coaching/consulting team while the necessary skills and rituals are implemented. For the task force to be successful, critical roles and skills are necessary. These include, but are not limited to, Business Analysts, Software Engineers, Agile coaches for Organizing Teams, and Data Analysts to measure the progress.
The task force is starting with the following goals to establish criterion for a successful implementation. These are based on a published case study for a company with a similar profile. The 6-month goals are as follows (Scaled Agile, 2022):
· 100% increase in software delivered to production
· 40% decrease in support tickets for production software
· 25% increase in employee satisfaction
As you will notice, the metrics for success are NOT related to the project metrics stated in the summary. The reason for this is the outcome is not more successful projects, but value delivered by software going to production. The project metrics stated in the summary highlighted the issue was the project management methodology, therefore the task force decided not to improve on those metrics as the analysis showed the data for the new agile delivery model to be incompatible.
Action Steps
The task force will start with the implementation of SAFe in the following steps.
1. Establish and execute a training plan
2. Coach and support two teams in the use of SAFe
3. Evaluate the progress based on the already stated metrics and adjust accordingly
4. After six months, decide as to the next steps with the goal of either dissolving or evolving the task force based on need after one year.
Risks & Mitigations
The XYZ company has identified several risks that include not just the success of the task force but also the overall implementation of Agile & SAFe.
Trust
Trust is the key to any successful delivery. The agile manifesto explains things that help a great deal with overcoming this critical issue. Agile methodology helps with empowering the team with trust in people than process. In addition to building trust among team members, it is equally important to have trust between customers. Complimenting this, the agile manifesto says customer agreements do not have to be comprehensive, but they can be stated project frameworks with delivery objectives. The important thing is all parties agree on a common goal with some flexibility. Embracing changes as the goes in the motto for Agile. Agile helps build a lot of trust and collaboration within the team (Petren, 2012).
Communication
Communication is the key to development, either professionally or personally. However, a lot of teams struggle with this issue. Agile brings business teamwork with the development team together and makes periodically progressive as the project proceeds. Agile helps eliminate any business-level misunderstanding that may occur during the development. The agile process asks for daily standups where teams discuss their daily operation and call out impediments. Agile brings the entire team together and leads to very few chances of miscommunication or misunderstanding of requirements. Traditional projects management values documentation, whereas the Agile management process measures success with software quality. A critical step of the agile methodology is to set up retrospective calls to analyze the process, identify the risks, and develop a plan to overcome the issues faced in the current iterations. All Agile promotes is to keep everyone in the team involved with every activity in the project and remove dependencies for better performance.
Ways of Working
A rigid environment is one of the most significant limitations of traditional project management. Agile gives unlimited flexibility. Agile will not have strict rules other than ensuring that the team is on the right path for delivery. In the midway of the project, any compliance policy or other essential factor requirements can be changed even if the total project design can be changed from scratch. Building a team-like task force may require making many changes, and Agile keeps it flexible with any unaccountable challenges when the project is started. With this team, efficiency can be improved without wasting a lot of resources. (Lazar, 2020)
Team participation
Many traditional projects failed due to the single person taking responsibility for delivering the project. In contrast, Agile methodology believes in valuing every team member’s participation in requirements, progress, and delivery. Agile gives more power to individual team players, which helps them to grow professionally. Great power always comes with significant responsibilities. This creates an incredibly supportive and open-minded environment that helps make many innovative ideas and develop creative solutions. (Lazar, 2020).
These risks will be consistently present throughout the implementation and will be revisited as part of the rollout. To build a team-like task force, we must stay accountable for many such challenges and potential risks, including those not mentioned above. The agile process stays flexible enough to overcome these issues and gives high productivity.
Resources
The task force will hire external agile consultants to successfully implement SAFe among the teams. Among the resources to hire, the most critical is the Agile coach. The agile coach will guide and train the team on Agile best practices throughout the implementation of SAFe (Lyssa Adkins, 2010). Agile coaches will help the team to effectively adopt SAFe methodology. Under the coach guidance the teams will start working in a scrum team with five to nine individuals who work toward completing the development projects and delivering products. The coach also leads workshops to teach agile concepts to the team.
Scrum master and a Business Analyst will be hired to work with the development teams to analyze the systems and come up with a plan of action to adopt agile best practices. SM will help team members to stay on track with scrum techniques. The BA will work with the task force to organize the requirement documents in the user story format. This will help the team to divide their work in different iterations/sprints. BA will also host Jira bootcamps, where the team will learn to basic of the tool and how to leverage it for tracking tasks and all work items. The task force will have the team go through an implementation training by Certified SAFe Program Consultants.
Terms & Definitions
Agile: Agile is an iterative approach to project management and software development that helps teams deliver value to their customers faster and with fewer headaches (Atlassian, 2022).
SAFe: Scaled Agile Framework for Enterprises (SAFe) is a knowledge base of proven, integrated principles, practices, and competencies for achieving business agility using Lean, Agile, and DevOps. (Scaled Agile, 2022).
Waterfall: is a sequential development process that flows like a waterfall through all phases of a project (analysis, design, development, and testing, for example), with each phase completely wrapping up before the next phase begins (Adobe, 2022).
References Comment by White, Nicholas: Need to be cleaned up Comment by White, Nicholas:
Adkins, L. (2010). Coaching agile teams: A companion for Scrum masters, Agile Coaches, and project managers in transition. Addison-Wesley.
Adobe. (n.d.). Waterfall methodology – A complete guide. Retrieved on January30th, 2022 from
https://www.workfront.com/project-management/methodologies/waterfall
Atlassian. (n.d.) What is agile? Retrieved January 31, 2022, from https://www.atlassian.com/agile
Balaji, S., & Murugaiyan, M. S. (2012). Waterfall vs. V-Model vs. Agile: A
comparative study on SDLC. International Journal of Information Technology
and Business Management, 2(1), 26-30.
Heriyanti, F., & Ishak, A. (2020, May). Design of logistics information system in
the finished product warehouse with the waterfall method: review literature.
IOP Conference Series: Materials Science and Engineering (Vol. 801, No. 1, p. 012100). IOP Publishing.
Lazar, S. (2020, June 16) Traditional versus Agile Project Management. NPR.
https://niftypm.com/blog/traditional-vs-agile-project-management-pros-cons/#
McManus, J., & Wood-Harper, T. (2007). Understanding the sources of information systems project failure.
Petrén, M. G. (2012). Trust—the key for successful delivery using agile methods. Paper presented at PMI® Global Congress 2012—EMEA, Marseilles, France. Newtown Square, PA: Project Management Institute.
Scaled Agile. (n.d.). SAFe. Retrieved on January 28th, 2022 from https://www.scaledagileframework.com
2/4/22, 6:20 PM Preview Rubric: Step 4 Scenario Testing Results (85 Points) – 3WI2022 Vir Ldrshp Global Based Teams (BADM-703-01B) – Indiana Wesleyan U…
https://brightspace.indwes.edu/d2l/lp/rubrics/preview.d2l?ou=157107&rubricId=482277&originTool=quicklinks 1/3
Step 4 Scenario Testing Results (85 Points)
Course: 3WI2022 Vir Ldrshp Global Based Teams (BADM-703-01B)
Criteria Excellent Competent
Needs
Improvement
Inadequate/Faili
ng
Criterion Score
Evaluation / 22
Recommendati
on
/ 22
22 points
The deliverable
demonstrates
the team’s ability
to thoroughly
evaluate the
effectiveness of
the solution in
multiple
scenarios.
Additional
scenarios are
evaluated.
20 points
The deliverable
demonstrates
the team’s ability
to adequately
evaluate the
effectiveness of
the solution in
multiple
scenarios.
18 points
The deliverable
demonstrates
the team’s
limited ability to
evaluate the
effectiveness of
the solution in
multiple
scenarios.
A lack of
scenario variety
limits the
evaluation.
15 points
The deliverable
demonstrates
the team’s
inability to
evaluate the
effectiveness of
the solution in
multiple
scenarios.
22 points
The deliverable
includes specific
recommendation
s for the
proposed
solution that
demonstrate the
team’s ability to
interpret their
evaluation.
20 points
The deliverable
includes specific
recommendation
s for the
proposed
solution.
18 points
The deliverable
includes some
general
recommendation
s for the
proposed
solution.
15 points
The deliverable
does not include
relevant
recommendation
s for the
proposed
solution.
2/4/22, 6:20 PM Preview Rubric: Step 4 Scenario Testing Results (85 Points) – 3WI2022 Vir Ldrshp Global Based Teams (BADM-703-01B) – Indiana Wesleyan U…
https://brightspace.indwes.edu/d2l/lp/rubrics/preview.d2l?ou=157107&rubricId=482277&originTool=quicklinks 2/3Total
Criteria Excellent Competent
Needs
Improvement
Inadequate/Faili
ng
Criterion Score
Teamwork / 22
Written
Communicatio
n
/ 19
22 points
Teammates
interact well by
offering their
own
understanding
and perspectives,
asking questions
about ideas,
sharing
responsibility,
and contributing
equally.
Teammates
demonstrate
effective
interpersonal
communication
and engage in
resolving
conflicts
together.
20 points
Teammates
interact to
adequately meet
expectations.
18 points
Teammates
attempt to work
with each other,
but demonstrate
limited
interaction or an
imbalance of
responsibility
that impedes
collaboration.
15 points
Teammates do
not communicate
well and/or
follow through
on individual
responsibilities
to achieve team
goals.
19 points
The deliverable is
presented
professionally
and is easy to
read and
understand. It
demonstrates
the effective
control of
grammar and
spelling.
In-text citations
and references
are correctly
formatted using
APA.
17 points
The deliverable is
presented
professionally
and is readable.
It demonstrates
the basic control
of grammar and
spelling, with
only minimal
errors.
In-text citations
and references
are correctly
formatted using
APA.
15 points
The deliverable is
lacking in
professional
presentation. At
times it is
difficult to read
or understand
due to issues
with grammar
and spelling.
In-text citations
and references
are attempted,
but incorrectly
formatted.
13 points
The deliverable
is not
professional. It is
difficult to read
or understand
due to many
issues with
grammar and
spelling.
No in-text
citations or
references are
appropriately
used.
2/4/22, 6:20 PM Preview Rubric: Step 4 Scenario Testing Results (85 Points) – 3WI2022 Vir Ldrshp Global Based Teams (BADM-703-01B) – Indiana Wesleyan U…
https://brightspace.indwes.edu/d2l/lp/rubrics/preview.d2l?ou=157107&rubricId=482277&originTool=quicklinks 3/3
Total
/ 85
Overall Score
Excellent
78 points minimum
Competent
69 points minimum
Needs Improvement
61 points minimum
Inadequate/Failing
0 points minimum
Step 4 Deliverable: Scenario Testing Results Template
Scenario: Reference the specific scenario. Identify the team member conducting the test of this scenario. |
Analysis: How would a team would use the Task Force Plan to work through this scenario? |
Action Steps: Recommendations for improving the solutions(s) within the plan to better address the scenario. |
Step 4 Deliverable: Scenario Testing Results Template
Scenario: Reference the specific scenario. Identify the team member conducting the test of this scenario. |
Analysis: How would a team use the Task Force Plan to work through this scenario? |
Action Steps: Recommendations for improving the solutions(s) within the plan to better address the scenario. |
Scenario #1 – (low performing team member – absence of trust)
|
The Task Force Plan does not directly address a low performing team member (absence of trust) but it does guide me in a direction that I can take to provide feedback to this scenario. The Task Force Plan mentioned how it will proactively strive to create “a company culture that truly values diversity”, while developing a process for forming and chartering global teams. Making sure that rapport is built, and everyone is being valued as a team player is a good way to open the lines of good, effective communication that will in return create an environment where the once team who was unwilling to ask for help, who was once vulnerable, who was afraid of admitting their mistakes which resulted in the absence of trust, will now be open to asking for help, not feel vulnerable, will admit their mistakes and own it, and build that much needed trust that will allow them to show up and learn from other group members. |
In the plan it was stated on Action Step Nine that in order to host successful virtual meetings the task force will take all initial and course corrective action to ensure our virtual meetings “build engagement, trust, and sincerity among teams” (Ferrazzi, 2015). I would recommend that it is enforced and stays enforced. As soon as a situation has been identified that has possibly caused a team member to behave in that manner, it needs to be immediately addressed before moving on. |
Scenario #2 – (Alpha leader) There is an ‘alpha’ person on the team. Although their role is not formal (yet) in terms of functioning as a team lead, they do. They are a taskmaster and often forge ahead without full buy-in from team members. They take little care over social niceties and are impatient with anything they see as a time-wasting distraction. This causes others to ‘check out’ because, well, Alpha will do ‘whatever’. One team member noted: “I have realized I am more hands-on in the project when one of the team members is less involved. This team member dominates the discussion. I tend to ‘sit back’ and contribute less when that happens.” |
Within the Task Force Plan, there are two action steps that address the issue of an alpha leader. These action steps combined create an environment of psychological safety that enables the team to move past an alpha leader by actively ignoring and engaging other members of the team when alphas attempt to take over. “In order to ensure everyone has a voice we will ensure clarity and alignment around “checking in often, finding a purpose or goal to unite around, having a balance of participation, and cultivating empathy” (Gavin, 2019). “In order to ensure each task force member has bought in and is accountable the team will host at least two workshops with the goal of creating necessary psychological safety and “cultivating interpersonal relations” (Hastings, 2018). |
In order to improve upon the solution as presented within the Task Force Plan, a revision can be made to further expand upon how balance will be achieved and maintained as well as provide clarity on the definition and understanding of psychological safety. The definition of psychological safety if not explicitly defined can be open to interpretation. |
Scenario #3 – (impasse – Fear of Conflict) In developing options for consideration, the team reaches an impasse. One team member gets into the weeds quickly and struggles with staying on ‘the main thing’. Although the team leans on their “Team Contract” for such situations, ultimately, they determine the Team Contract is not specific enough to provide remedy. These pauses add time to everyone’s already busy schedules and has happened more than once. The end result is a fear of conflict which in turn results in team members incapable of engaging in debates. |
In anticipation of issues such as this the team contract states: “The priority of Backlog items (tasks / action items) will be reviewed at the top of the meeting to ensure we are dedicating our time to discussing only items of utmost importance when considering magnitude of the problem we are attempting to solve or the business value we are attempting to create.” However, the contract doesn’t specifically detail how to handle disagreement on priority or refusal to follow the priority agreed to by the majority. Furthermore, the contract doesn’t specifically have a conflict resolution clause. |
If and when there is a measure of disagreement on the priority of tasks and lack of clarity around the importance of the “main thing,” a “Backlog Grooming Session” will be held with the sole goal of aligning to the importance of the main thing and gaining agreement on order of priories. Whenever there is conflict or disagreement a third-party arbitrator / mediator will be brought in from the respective team’s senior leadership. A meeting will be held to determine, without question, what is the priority and reaffirm the importance of focusing on “the main thing.” The conflict resolution clause will have verbiage to address how to handle a second infraction of this policy which would likely result in dismissal from the task force. |
Scenario #4 – (VBM/Staffing) The team is tasked to create a Task Force to address critical business issues, demonstrate virtuous leadership, and implement the VBM model in its work. The team struggles with the resource aspects of ‘how to identify candidates for the Task Force that would implement the VBM model’. The right fit is critically important – essentially the difference between success and failure. What actions can the team advance to identify these candidates and achieve the right fit, right role, right time for the success of the project? |
In the Executive Summary and under the section Objectives, it is identified that there are shared cultures and values of the company that need to also be reproduced within the task force. The first shared culture and value identified is virtuous leadership. If virtuous leadership was important enough to be identified first for the shared culture and values of the company, then if the task force is having problems identifying candidates who would implement the VBM model then there is perhaps a larger problem in the company. Call employees of the company should be adhering to the corporate values of virtuous leadership. Therefore this issue should not arise unless the company is straying away from its corporate values. In the case that the company has strayed away from its corporate values, Action Step Ten should be implemented. This Action Step states: In order to ensure the proper leaders have been selected for the task force, and more importantly, these leaders uphold their role we will vow to tolerate nothing less than behavior exuding the values of “courage, respect, reconciliation, cooperation, and inspirer (Brooker & Boyce, 2017). Furthermore, this considering must live in perpetuity to ensure sustainability as indicated by Caldwell and Hayes (2016). Initial success will be far outweighed by long term success. |
We could include the company’s value statement in the project. |
Scenario #5 — (lack of passion – Inattention to Results) Part of the team is working overtime to make up for other members who do not feel as passionate or accountable about getting this project completed in an excellent manner. These team members tend to put their own needs (ego, recognition, career development) ahead of the team goals. This results in the team losing sight of the ‘main thing’ and the project suffers. As a team functioning to model the VBM, how do you balance grace and holding people accountable for their actions/inactions? How do you handle what feels like disengagement from team members? |
LPKWW has clearly outlined the corporate values and policies and according to the Task Force Plan under the sections of “Keys to Success” and “Objectives”, the global task force must function within the guidelines of the shared, promoted, and expressed corporate cultures and values including virtuous leadership, servant leadership, ethical business practice, moral decision making, as well as with the respect of cultural differences and practices As a team functioning to model the VBM, all team members should adhere to the corporate values to help balance grace when holding others accountable for their actions/inactions. Per Action Step Three, the team will host at least two workshops with the goal of creating necessary psychological safety and “cultivating interpersonal relations” (Hastings, 2018) in order to ensure that each task force member is brought in and held accountable. This will also help with what may feel like the disengagement from team members. Action Step Two will also assist with the mishaps of disengaged team members by ensuring that all task force members have a voice and will ensure clarity and alignment by “checking in often, finding a purpose or goal to unite around, having a balance of participation, and cultivation empathy” (Gavin, 2019). |
For improving the solution within the plan to better address balancing grace and holding individuals accountable for their actions/inactions, I would recommend adding to Action Step Six with bulletins clarifying that all team members must contribute in some aspect during one of the two workshops. I believe formalizing that all task force members must engage at the workshops will also help with handling disengagement from team members. |
Scenario #6 – (ESL) As a global -based team comprised of colleagues who are not centrally located, the team is expectedly diverse – with members in different time zones, different language dialects, different norms. At times, it is difficult to fully understand what some members are saying when they speak (on ZOOM calls, or other telecom means). As a team that is modeling the VBM, what approaches or tools can be utilized to bridge any language or comprehension gaps? In the absence of this, what are the projected outcomes? Why is this important? |
In order to bridge the language or comprehension gap we will first utilize Action Step Two: In order to ensure everyone has a voice we will ensure clarity and alignment around “checking in often, finding a purpose or goal to unite around, having a balance of participation, and cultivating empathy” (Gavin, 2019). Furthermore, the task force will proactively strive to create “a company culture that truly values diversity, developing a process for forming and chartering global teams, offering intercultural communication training, and offering conflict management training for teams are also ways in which one could handle conflict within a global team” (Curry, 2016). Then, when addressing the tools needed to meet this scenario, we would implement Action Step Nine: In order to host successful virtual meetings the task force will take all initial and course corrective action to ensure our virtual meetings “build engagement, trust, and sincerity among teams” (Ferrazzi, 2015). This is very important because without open, honest, diverse, and trusted communications, the team will not function efficiently or to its full capacity. Communication is the fuel that makes the team perform. Without communication, you will lose performance. |
Be more defined in how we address all aspects of team diversity and how it effects dialogue. |
References:
Brooker, M., & Boyce, J. (2017, Spring/Summer). Virtuous leaders & organizations. The DeVoe Report, 56-60. https://www.indwes.edu/academics/caps/devoe-school-of-business/the-devoe-report/archive/the_devoe_report_spring17.pdf
Caldwell, C., & Hayes, L. A. (2016). Self-efficacy and self-awareness: Moral insights to increased leader effectiveness. The Journal of Management Development, 35(9), 1163-1173. https://doi.org/10.1108/jmd-01-2016-0011
Curry, C. (2016, February 4). Managing conflict in global teams. Training Magazine. https://trainingmag.com/trgmag-article/managing-conflict-global-teams/
Ferrazzi, K. (2015, March 27). How to run a great virtual meeting. Harvard Business Review.
https://hbr.org/2015/03/how-to-run-a-great-virtual-meeting
Gavin, M. (2019, May 16). 4 Tips for managing global teams. Business Insights: Harvard Business School.
https://online.hbs.edu/blog/post/how-to-manage-global-teams