Orange = Business, Green = IT
This was the last part of our small Series about Agile Project Management
The whole Series contains 4 pieces:
Agile Project Management – Basics (Part1) Agile Project Management – What is SCRUM (Part2) Agile Project Management – Agile Project Management in real Life (Part3) Agile Project Management – Agile on the next Level – Program Management (Part4)
If you have any comments on our Articles, your Feedback is highly welcome.
Despite the difficulties especially at the beginning of the project, it is still very well in time. This is caused by the fact that the team always kept working and the project was never unable to go on. Due to the agile nature of the project in time communication and transparency were possible!
This was the third part of our small Series about Agile Project Management. Look out for the next part which we are going to publish soon called "Agile Project Management – Agile on the next Level - Program Management"
Today we start with our short series about agile Project Management with this first article.
Nowadays almost everyone (at least in IT environments) talks about agile project management methods. Some already checked them out, but often enough there are some counter positions to these methods which are related to some unclear things within the methodology.
This small series will try to describe in detail what agile project management is and what are the success factors. First of all: agile project management is a methodology and a mindset! It is NOT a strictly designed process, which will solve problems magically. Key points of "agile" are:
Agile Project management works iterative, the product AND the process will be reviewed and optimized after each iteration
The highly collaborative structure focuses on teamwork and end user transparency as in showing actual project progress or problems which slowed down the progress
At the end of each iteration there will be a product increment which can be used by the customer, this creates actual value and ROI even before the end of the project
Agile Project management can be used in nearly all custom development projects.
If your project has 100% fixed requirements, which will surely not change during the project (by the way...just because they are written down, it does not mean they are fixed!)…
If you roll out "commercial off-the-shelf" software, which is already packaged and automatically distributed (think about MS Office for example)... If your project deals with upgrading or patching a system… … then agile might not be the right approach. If you are thinking about doing your own agile project it is highly recommended to involve an already agile-experienced colleague as an "Agile-Coach". He can help you to set up the process and working mode and help to get a clear understanding what agile is about. Here are some doubts which are quite common regarding agile methods:
This was the first part of our small Series about Agile Project Management. Look out for the next part which we are going to publish soon called "Agile Project Management – What is SCRUM"
In the preparation of this article, we discussed several ideas, how to introduce Scrum to you. In search of inspirations we have found the introduction video from the Scrum alliance.
In the end, this is a pretty short 80-seconds introduction to Scrum, which we would like to show to you, instead of reinventing the wheel again.
In addition to the video we would like to share more information:
Scrum is very good when it comes to establishing agile methods into an organization. By providing a simple approach it can easily be picked up and enhanced. Also Scrum is very well known and there are lots of experienced Scrum Coaches in the outside world of Covestro.
Scrum is a framework which provides a basis of 3 roles, 4 activities and 3 artifacts, which will now be explained in detail.
Each Scrum implementation is different though. Depending on the project or the organization there will be additional roles or activities. Scrum focuses on communication and collaboration by discussing requirements and short feedback cycles, which is the most important thing to keep in mind.
In the following we want to explain the different roles, activities and artifacts. Furthermore we want to provide you a check list what you have to prepare for your first Scrum project.
User Stories
A simple method to describe requirements, by a user's perspective, with only one or a few sentences. Usually a user story consist of Who? What? And Why?
e.g.: "As a user I want to be able to back up my data in order to recover it in case of an error."
User stories are constantly refined and extended during the project. They are the basis for discussion about the features. This will help to get a clear understanding of the requirements.
Sprint
An iteration of Scrum which is usually between 1 and 4 weeks long. Or in other words: This is the timeframe, in which work is planned continuously. Once the duration is set it should not be changed during the project though.
Artifacts
Artifacts provide information about the product, the requirement and the progress. The scrum team permanently works with the artifacts. For instance, an artifact is the list of requirements which are known so far.
Activities
Activities are mostly meetings which are part of each sprint. (The sprint itself can be seen as an activity too) By discussing and/or working with the artifacts during the activities, the project progress and obstacles become transparent.
Definition of Done
A project specific agreement which defines when a user story is completed.
This was the second part of our small Series about Agile Project Management. Look out for the next part which we are going to publish soon called "Agile Project Management – Agile Project Management in real Life"
Exchange Server vNEXT ist nichts anderes als der Platzhaltername für die nächste Version von Exchange Server, die als Nachfolgeversion von Exchange Server 2019 veröffentlicht werden wird, da der finale Produktname noch nicht feststeht.
Nach der Veröffentlichung von Exchange Server 2019 gab es immer wieder Spekulationen, ob dies nun die letzte Exchange Server Version ist und damit das Ende von lokalen Exchange Server Editionen eingeläutet wurde. Während der Microsoft Ignite 2020 Konferenz hat Greg Taylor die Vision für Exchange Server vNEXT vorgestellt und damit den Spekulationen ein Ende gesetzt.
Die Veröffentlichung von Exchange Server vNEXT ist für das zweite Halbjahr 2021 angekündigt und wird nun die letzte On-Premises Version von Exchange Server sein. Welche technologischen Neuerungen Exchange Server vNEXT für Anwender bieten wird, ist zum jetzigen Zeitpunkt noch unklar.
Die wichtigste Änderung, die uns mit Exchange Server vNEXT treffen wird, ist die Änderung des Lizensierungsmodells. Mit der nächsten Version von Exchange Server erfolgt ein Wechseln zu einer Abonnement-basierten Lizensierung. Wie die Lizensierungsbedingungen im Detail aussehen werden und wie sich die neue Lizensierung preislich darstellen wird, ist aktuell noch nicht bekannt. Mit dem Wechsel zu einem Abonnement-Modell werden Kunden auf jeden Fall thematisch an die Abonnement-Modelle der Microsoft-Cloud-Dienste herangeführt.
Zum ersten Mal in der Geschichte von Exchange Server, ermöglicht Exchange Server vNEXT eine direkte Aktualisierung einer Exchange Server Installation. Diese In-Place-Aktualisierung ist jedoch nur für Exchange Server 2019 vorgesehen. Wenn Sie planen, auch in Zukunft weiterhin Exchange Server in einer lokalen IT-Infrastruktur einzusetzen, ist nun die Zeit gekommen, auf Exchange Server 2019 zu wechseln. Nur so profitieren Sie von einer einfachen Aktualisierung auf Exchange Server vNEXT. Die Möglichkeit zur In-Place Aktualisierung ist jedoch zeitlich beschränkt. Ab dem Zeitpunkt der Veröffentlichung von Exchange Server vNEXT beginnt das zweijährige Zeitfenster, in dem ein In-Place Upgrade eines Exchange Server 2019 Systems, mit aktuellem kumulativem Update, möglich sein wird.
Mit der Änderung des Lizensierungsmodells ändert sich auch die Bereitstellung von Produktaktualisierungen und dem Zugang zum Produktsupport für Exchange Server vNEXT. Sie erhalten zukünftige Softwareaktualisierungen und Support nur, wenn Sie über ein aktives Abonnement für Exchange Server vNEXT verfügen.
Exchange Server vNEXT erlaubt einen Koexistenzbetrieb mit allen modernen Exchange Server Versionen ab Version 2013. Dies ist eine Abweichung von früheren N-2 Voraussetzungen, als nur die jeweils aktuelle Produktversion und die jeweils beiden Vorversionen in einer Koexistenz betrieben werden konnten.
Da sich Exchange Server 2013 und 2016 bereits in der erweiterten Supportphase befinden, ist es Zeit, sich Gedanken über eine Migrationsstrategie zu machen. Je nach Ausgangssituation und geplantem Betriebsszenario einer lokalen Exchange Organisation, ergeben sich unterschiedliche Optionen.
Exchange Server 2016 befindet sich zwar seit dem 13. Oktober 2020 in der erweiterten Supportphase, jedoch ist diese die passende Produktversion, um einen reinen Verwaltungsserver für eine Hybrid-Konfiguration zu betreiben. Im Rahmen Ihres Microsoft 365 Abonnements können Sie eine kostenlose Lizenz zum Betrieb des Koexistenz-Servers erhalten. Für Exchange Server 2019 steht diese Option nicht zur Verfügung, da diese Produktversion immer eine kostenpflichtige Lizenz erfordert.
Die Daten für die Supportzeiträume von Exchange Server 2019 haben eine wichtige Änderung erfahren. Für Exchange Server 2019 war nie eine fünfjährige Phase für den erweiterten Support geplant. Exchange Server 2016 und 2019 hatten schon immer den 14. Oktober 2025 als finales Supportende. Das Ende des Mainstream-Supports für Exchange Server 2019 wurde vom 1. September 2024 auf den 9. Januar 2024 vorgezogen.
Das folgende Diagramm verdeutlicht noch einmal die Supportzeiträume moderner Exchange Server Versionen und das Zeitfenster für ein mögliches In-Place-Upgrade auf Exchange Server vNEXT.
Die Ankündigung von Exchange Server vNEXT gibt Exchange Administratoren Zuversicht und Planungssicherheit für den Betrieb einer lokalen Exchange Server Organisation. Jedoch ändern sich durch neue Lizensierungsmodelle die Voraussetzungen für den Betrieb. Wenn Sie die Anforderung nach einer hochverfügbaren Bereitstellung von Exchange Server Funktionen haben, gibt es zwei Möglichkeiten:
Für welchen Weg Sie sich auch entscheiden, Exchange Server blickt auf mehr als 25 Jahre Erfahrung in der Bereitstellung einer soliden Messaging-Plattform zurück.
Viel Spaß mit Exchange Server.
Mailscape 365 - Überwachung von Hybrid Exchange und Office 365: Viele Unternehmen verwenden eine lokale Exchange Organisation und Exchange Online in einer Hybrid-Konfiguration, um die Anforderungen ihrer Mitarbeiter zu erfüllen. Der Betrieb einer hybriden Exchange Organisation seine ganz eigenen Herausforderungen für das Monitoring der Dienstverfügbarkeiten. Beginnen Sie noch heute einen unverbindlichen 14-Tage Test von Mailscape 365.
While trying to synchronize a new device with an Exchange mailbox, you receive an error with your new mobile phone partnership.
The Exchange Server 2010 Default Throttling Policy is configured to accept 10 ActiveSync devices per mailbox only.
You can validate this setting by using EMS
Get-ThrottlingPolicy def* | Select Name,EASMaxDevices
Use a scheduled PowerShell script to delete old ActiveSync Device partnerships that have not been used for a defined period of time.
Find the most recent version on TechNet Gallery and Github, following the links provided in the Links section.
Modifiy the script path variables to fit your requirements. The variables are configured in the ### BEGIN Variables section.
Steps being executed:
<# .SYNOPSIS Remove Exchange Server 2010 ActiveSync Device Partnerships Sebastian Rubertus / Thomas Stensitzki THIS CODE IS MADE AVAILABLE AS IS, WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK OF THE USE OR THE RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER. Send comments and remars to: support@granikos.eu Version 1.0, 2015-04-09 .LINK More information can be found at http://www.rubertus.net/Blog/tabid/85/EntryId/41/Scripted-removing-of-ActiveSync-Device-Partnerships.aspx .DESCRIPTION THis script removes ActiveSync device association from user mailboxes that have been inactive for more than 150 days. .NOTES Requirements - Exchange Server 2010 - Windows Server 2008 R2 SP1, Windows Server 2012 or Windows Server 2012 R2 Revision History -------------------------------------------------------------------------------- 1.0 Initial community release .EXAMPLE Remove-ActiveSyncDevicePartnership #> ### BEGIN SnapIns ------------------------------------------------------------- # Add Exchange SnapIn if not already loaded if ( (Get-PSSnapin -Name Microsoft.Exchange.Management.PowerShell.E2010 -ErrorAction SilentlyContinue) -eq $null ) { Add-PsSnapin Microsoft.Exchange.Management.PowerShell.E2010 -ErrorAction SilentlyContinue if ( (Get-PSSnapin -Name Microsoft.Exchange.Management.PowerShell.E2010 -ErrorAction SilentlyContinue) -eq $null ) { Write-Host "Microsoft.Exchange.Management.PowerShell.Admin could NOT be loaded!" -ForegroundColor Red Write-Host "Verify that the Exchange 2010 Management is installed on this computer!" -ForegroundColor Red } } ### END SnapIns --------------------------------------------------------------- ### BEGIN Variables | EDIT ACCORDING TO YOUR NEEDS ---------------------------- # ScriptPath $scriptPath = "C:\Scripts\Remove-ActiveSync-Devices\" # Logfile $logfile = "C:\Scripts\Remove-ActiveSync-Devices\Logs\$(get-date -format yyyy-MM-dd___HH-mm-ss)___Logname.log" ### END Variables ------------------------------------------------------------- ### BEGIN Functions ----------------------------------------------------------- Function Log { Param ([string]$logstring) Add-content $logfile -value "$(get-date -format yyyy-MM-dd___HH-mm-ss) $logstring " } ### END Functions ------------------------------------------------------------- ### BEGIN Main ---------------------------------------------------------------- # Create a new log file Write-Host Write-Host "Script started, creating Log File." Log "Script started." Write-Host # Query User Mailboxes and Device Statistics Write-Host "Querying User Mailboxes, please wait a few seconds..." -ForeGroundColor green Log "Querying User Mailboxes." Write-Host $Mailboxes = Get-Mailbox -RecipientTypeDetails UserMailbox -ResultSize Unlimited -WarningAction SilentlyContinue $NumberOfMailboxes = $Mailboxes.count Write-Host "Number of Mailboxes: $NumberOfMailboxes " Log "Number of Mailboxes: $NumberOfMailboxes " Write-Host # Iterate each User Mailbox ForEach ($Mailbox in $Mailboxes) { $MailboxAlias = $Mailbox.Alias Write-Host Write-Host "=================================================================================" Write-Host Write-Host "Getting ActiveSync Devices from user $MailboxAlias..." Log "Getting ActiveSync Devices from user $MailboxAlias. " $AllDevicesFromSpecificUser = Get-ActiveSyncDevice -Mailbox $MailboxAlias -Result Unlimited -WarningAction SilentlyContinue | Get-ActiveSyncDeviceStatistics -WarningAction SilentlyContinue $AllDevicesFromSpecificUserNotSynchronizedSince150Days = Get-ActiveSyncDevice -Mailbox $MailboxAlias -Result Unlimited -WarningAction SilentlyContinue | Get-ActiveSyncDeviceStatistics -WarningAction SilentlyContinue | Where {$_.LastSuccessSync -le (Get-Date).AddDays("-150")} Write-Host $CountAllDevicesFromSpecificUser = $AllDevicesFromSpecificUser.Count $CountAllDevicesFromSpecificUserNotSynchronizedSince150Days = $AllDevicesFromSpecificUserNotSynchronizedSince150Days.Count If ($CountAllDevicesFromSpecificUser -lt 5) { Write-Host "User $MailboxAlias has only $CountAllDevicesFromSpecificUser ActiveSync Devices. Nothing to delete!" -ForegroundColor Green Log "User $MailboxAlias has only $CountAllDevicesFromSpecificUser ActiveSync Devices. Nothing to delete!" } If (($CountAllDevicesFromSpecificUser -gt 4) -and ($CountAllDevicesFromSpecificUserNotSynchronizedSince150Days -gt 1)) { Write-Host "User $MailboxAlias has $CountAllDevicesFromSpecificUser devices. $CountAllDevicesFromSpecificUserNotSynchronizedSince150Days have not synced for more than 150 days." -ForegroundColor Red Log "User $MailboxAlias has $CountAllDevicesFromSpecificUser devices. $CountAllDevicesFromSpecificUserNotSynchronizedSince150Days have not synced for more than 150 days." ForEach ($Device in $AllDevicesFromSpecificUserNotSynchronizedSince150Days) { $DeviceType = $Device.DeviceType $DeviceFriendly = $Device.FriendlyName $DeviceID = $Device.DeviceID $DeviceFirstSyncTime = $Device.FirstSyncTime $DeviceLastSuccessSync = $Device.LastSuccessSync Write-Host Write-Host "ActiveSync Device 2 delete Properties: " Write-Host "-------------------------------------- " Write-Host "Type : $DeviceType " Write-Host "Friendly Name: $DeviceFriendly " Write-Host "ID : $DeviceID " Write-Host "Last Sync : $DeviceLastSuccessSync " -ForegroundColor Red Log "Removing Device $DeviceType with ID $DeviceID ..." Write-Host Write-Host "Removing Device $DeviceID ..." -ForegroundColor Red $Device | Remove-ActiveSyncDevice -WarningAction SilentlyContinue } } } # Script finished Write-Host Write-Host "Script finished!" Write-Host Log "Script finished!" ### END Main ------------------------------------------------------------------
You need assistance with your Exchange Server setup? You have questions about your Exchange Server infrastructure and going hybrid with Office 365? Contact us at office365@granikos.eu or visit our website http://www.granikos.eu.
ENow has released version 7.0 of the ENow Management System (EMS).
Besides a major facelift of the OneView Dashboard new functionality has been added to the successful monitoring and reporting solution:
Request your free 21-day trail today: http://www.granikos.eu/en/mailscape