diff --git a/CHANGELOG.md b/CHANGELOG.md index 581a0065..574c6108 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,6 +6,27 @@ Note: Changelog started in January, 2021 +## November, 2024 + +### New Articles - November, 2024 + +| Article | Principal Author | +|---|---| + +### Updated Articles - November, 2024 + +| Article | Updated By | +|---|---| + +### Removed/retired Articles - November, 2024 + +| Article | Updated By | +|---|---| + +### New Contributors - November, 2024 + +- + ## October, 2024 ### New Articles - October, 2024 diff --git a/Community/includes/mm4m365-core-team.md b/Community/includes/mm4m365-core-team.md index de38e957..d00c92cf 100644 --- a/Community/includes/mm4m365-core-team.md +++ b/Community/includes/mm4m365-core-team.md @@ -1,13 +1,16 @@ The MM4M365 core team has evolved over time and these are the people who have been a part of it. -**Core team**: +**Core team** - [Marc D Anderson, MVP](https://www.linkedin.com/in/marcanderson) -- [Sharon Weaver](https://www.linkedin.com/in/sharonweaver/) - [Simon Hudson, MVP](https://www.linkedin.com/in/simonjhudson/) - [Simon Doy, MVP](https://www.linkedin.com/in/simondoy/) +- [Sharon Weaver](https://www.linkedin.com/in/sharonweaver/) +- [Galen Keene](https://www.linkedin.com/in/galenkeene/) +- [Pia Langenkrans](https://www.linkedin.com/in/pialangenkrans/) +- [Mats Warnolf](https://www.linkedin.com/in/matswarnolf/) -**Emeritus**: +**Emeritus** - [Sadalit (Sadie) Van Buren](https://www.linkedin.com/in/sadalit/) - [Emily Mancini, MVP, UXMC](https://www.linkedin.com/in/eemancini/) diff --git a/Community/microsoft-maturity-model-how-to-people-communities.md b/Community/microsoft-maturity-model-how-to-people-communities.md index cab02960..35dd7aed 100644 --- a/Community/microsoft-maturity-model-how-to-people-communities.md +++ b/Community/microsoft-maturity-model-how-to-people-communities.md @@ -36,7 +36,7 @@ To advance to the 200 level, consider the following activities: Focus on known working groups, like project teams and departments, to begin transitioning to [Microsoft 365 Groups](https://support.microsoft.com/office/learn-about-microsoft-365-groups-b565caa1-5c40-40ef-9915-60fdb2d97fa2) or [Dynamic Distribution Groups](/Exchange/recipients/dynamic-distribution-groups/dynamic-distribution-groups) (when file management or additional collaboration outside of email is not needed). These working groups are considered the "inner loop" which is a known set of people working together. The members and output are clearly defined simplifying the choice of what-to-use when. - A project team needs to communicate updates internally and collaborate on files. A Microsoft 365 Group will provide a shared calendar, email distribution list, SharePoint Team Site, and the potential to add a Microsoft Team for a robust meeting space with persistent chat. Project communication should shift to SharePoint news, the associated Microsoft 365 Group email distribution list, or Teams chats. +A project team needs to communicate updates internally and collaborate on files. A Microsoft 365 Group will provide a shared calendar, email distribution list, SharePoint Team Site, and the potential to add a Microsoft Team for a robust meeting space with persistent chat. Project communication should shift to SharePoint news, the associated Microsoft 365 Group email distribution list, or Teams chats. A department, depending on the size and company culture, may also benefit from a Microsoft 365 Group. Large departments where all members are not actively collaborating may be best served by a Dynamic Distribution Group as communication is primarily one way and the smaller functions within the department are then collaborating with Microsoft 365 Groups.