Agile scrum using ms teams share point saturday utah

Editor's Notes

1. The video was from a TedX promotion and while not only being a beautiful piece, represents how we think of Agile. Agile or Scrum in terms of project management is the division of tasks with frequest reassessments and adaptation of plans. A Kaleidoscope is similar in that it’s constantly changing or moving of objects and elements.
2. In Feb of 2001…just about 17 years ago, a group of people met at the Lodge at Snowbird ski resort right here in Utah to develop what would be known as the Agile Manifesto. There were representatives from various disciplines and all considered experts in their field of study. Since then, principles of the Agile Manifesto have been adopted into businesses worldwide. However, there are very few companies that are truly agile…most fall under using some type of Agile or Scrum tools, but would still be considered Waterfall or various other combination names like Scrumfall, or Fragile.
3. At the heart of the Agile principles is that it puts the focus back on the team. Processes are defined by the team, the team decides what support systems to use and what is needed to get the job done. The focus on the team is a critical aspect and inspired such phrases like “working out loud”. However, it’s important to remember, these concepts were developed for a team of people that were co-located originally. Many of the tools and techniques work best for a team that is all in one place. This doesn’t mean the team NEEDS to be co-located, but they may have to work a little different and select different tools when working with teams that are virtual.
4. By Dr ian mitchell - Own work, CC BY-SA 4.0, https://commons.wikimedia.org/w/index.php?curid=44894952
5. Daily Standup meeting. Short, quick meetings to discuss 3 things: What did you complete yesterday, what will you work on today, any roadblocks in the way?
6. A common misperception in using Agile/Scrum is that there is no documentation. In reality, there is documentation, it’s just not done in the same way. Documentation can be through conversations, discussions, meetings, whiteboarding activities or whatever else it takes to get the work compeleted. It focuses on working pieces or MVP (Minimal Viable Products) rather than bullet proof documentation that is hard to understand for the normal user and can be hard to find.
7. Typically a team in Scrum is small—roughly around 7-8 people. It can include ancillary team members however such as product owners from different areas that provide a rich set of requirements that in turn develop user stories. Microsoft teams allows for that collaboration with different team members, both inside and outside the company. As of right now, as many as 2500 team members can be added to a specific Team, this is an increase over the previous 999. I’m not sure if it’s wise to have a group that large, however, especially when working on a project, but it could be useful for other purposes. You can also add members from outside the organization as long as there is an Azure AD account associated with it.