Idle teams

(Continued from Portfolio Management Part 1 in the Scrum Alone is Not Enough series.)Imagine that the Portfolio Management group is giving the individual Product Owners a budgetary envelope of an approximate size. As Product Owners, we expect to make small bets on individual User Stories that will deliver value to the customer. The Portfolio Management group wants to make mid-sized bets (>1 Team Sprint) that will deliver value to the customer.But let’s say the current Sprint is one in which some Team members don’t really have a lot to do. This is the type of scenario that often drives management crazy because they see idle workers, and traditional thinking is that idle workers don’t deliver value. This rarely ever happens in real life because there’s almost always more work than there is Teams to do it, but should the rare situation occur when one doesn’t have work in the current Sprint, questions that arise may be things like:should we temporarily reassign those Team members to other teams/projects that are lagging behind, to help them catch up?should we give them a feature that is further down the road in the backlog to work on in the meantime, with the thinking that it will give us a head start on it since they’re sitting idle anyway?The answer is, of course, to do neither.If the ‘idle’ Team were to join another Team temporarily, it wouldn’t speed things up – just the opposite, it would slow everything down. Disrupting that Team’s effectiveness and cadence, their contribution would be much smaller than their effect in reducing the other Team’s capacity. In addition, it could harm moral by suggesting that the other Team can’t handle the tasks themselves.And if the idle workers start developing a Feature that is further ahead on the Backlog, it undermines the Product Owner and Portfolio Management’s priority settings and decisions, which leaves room for “hey, could you do me a quick favour” requests within the Sprint that weren’t in the Sprint backlog. By the time the rest of the Team gets to that feature in the backlog, they may find that the work the idle Team had made on it is obsolete and needs to be undone before they can make new progress.The best solution is have ‘idle’ Team members look at the board and see if there are bottlenecks that they can help with within their own Team. They could also pay down their technical debt, or spend time learning something that expands their capacity as a Team to work outside of their current area/column(s) on the Kanban chart. For example, the Team in the previous examples might teach themselves something about testing or creating effective online help.The most effective

CollabOS Power Management helps you deploy your video conferencing rooms in an energy-efficient manner. Take control of your device's energy consumption with features like power savings mode, HDMI CEC support, and auto wake-up.Logitech CollabOS devices including Rally Bar, Rally Bar Mini, Rally Bar Huddle, RoomMate, Tap IP, and Tap Scheduler support Microsoft Teams Rooms Office Hours and Zoom Rooms Device Operation Time and Idle Time-Out.FeaturesRally BarRally Bar MiniRally Bar HuddleRoomMateTap IPTap SchedulerPower Saving Mode 1✓✓✓✓✓-Auto wake up using AI viewfinder✓✓----Auto wake up using Tap sensor✓2✓2✓2✓2✓-Touch to wake✓2✓2✓2✓2✓2✓Turn off display (HDMI CEC)✓✓✓✓--1. After 10 minutes of inactivity in the room, the power saving mode will start. Supported TVs will be turned off if they are inactive.2. Requires a Tap or Tap IP or a Touch Display to be connected to the room system.Note: CollabOS devices use CEC to turn displays on and off, we recommend testing your display's CEC support for ensuring compatibility.Service Provider SettingsCollabOS power management configurations are specific to service provider settings. For Microsoft Teams Rooms and Zoom Rooms please follow the instructions from the service provider.Microsoft Teams Rooms on AndroidWhen using Teams, the CollabOS power-saving setting is disabled since this setting is managed by the Teams Admin Center. FeaturesRally BarRally Bar MiniRally Bar HuddleRoomMateTap IPTap SchedulerIdle Mode✓✓✓✓✓-Office Hours✓2✓2✓2✓2✓2✓1Auto wake up using AI viewfinder✓✓----Auto wake up using Tap sensor✓✓✓✓✓-Touch to wake✓✓✓✓✓✓Turn off display (HDMI CEC)✓✓✓✓--By default, office hours schedule 8 am - 5 pm is appliedPower saving settings in Teams Admin Center must be disabled for Office hours to applyOffice HoursCollabOS devices will have office hours enabled by default from 8 am to 5 pm, even if a configuration profile is not pushed. To configure a different office hours setting, create a Teams configuration profile in Teams Admin Center and push it to the device. Here are different scenarios and their corresponding results. ScenarioResultDuring Office hours (e.g. 8am - 5pm)Display will not turn offOutside office hours (e.g. 5pm - 8am)Displays will turn offOutside office hours (Motion detected)Displays will turn onOutside office hours (Person detected)Displays will turn onOutside office hours (No person or motion detected)Displays will turn off after 10 minutesIdle ModeIdle mode means that the device wakes up only when it is being used or when motion of people are detected in the room. When there is no activity, motion, or people detected, the device will go to sleep. To enable "Idle Mode" with Teams, you can set a short office hours time span, for example, 07:00 am - 08:00 am. This ensures that the displays are on for only 60 minutes. After that, the device will remain in power saving mode until a meeting is started or motion or people are detected. Auto wake up displays when people or motion is detectedIf you want the display to turn on automatically when a person or motion is detected, you need to enable CollabOS setting "Auto wake up using AI viewfinder" for people detection and "Auto wake up using Tap sensor" for motion detection. This feature only applies outside scheduled

Layout" panel.[*] Configuration: Windows are now properly scaled at startup to conform with the DPI resolution set for a monitor, which they are opening on.[*] Mirroring: Now you can toggle the mirrors full-screen using the left double click or pressing Alt-Enter/F11. Also, you can exit full-screen by pressing Esc.[*] Wrap Desktop: The feature has been rewritten from scratch to provide more predictable and expected behavior, especially on non-uniform desktop configurations.[-] Actual Taskbar, Windows 7+: Programs running with administrative privileges can't be minimized by clicking their task button.[-] Actual Taskbar, Windows 7+: Preview thumbnails were not scaled correctly in high DPI resolutions.[-] Actual Taskbar, Windows 10: Preview thumbnails looked differently than in the system taskbar.[-] Desktop Divider: In some cases the "Put into" dialog did not display some tile layouts in full.[-] Save Idle Screens: Numerous fixes in the automatic mode: - idle screen saver did not start on a primary monitor in Windows 10 if Actual Multiple Monitors was installed with the support of system utilities and administrative tools - idle screen saver stopped if the Desktop itself was activated - idle screen saver did not restart after closing it because of moving the mouse - idle screen saver can't be stopped on a monitor disconnected and then connected back - idle screen saver can't be stopped after switching to another user account and then returning back - the feature ignored mouse movements on monitors with no active window[-] Drag to Scroll, Windows x64: The feature didn't work for 32-bit applications unless its activation mouse button was set to "left".[-] Easy Window Dragging/Sizing, Windows x64: The feature didn't work for 32-bit applications.[-] Easy Window Dragging/Sizing, Windows 10: The feature didn't work for UWP applications (e.g. Settings, Skype, Store, Xbox, Calculator, etc.).[-] Easy Window Dragging/Sizing: The feature didn't work for Chromium-based applications (e.g. Google Chrome and Vivaldi web browsers, Slack desktop client, Microsoft Teams desktop client, etc.).[-] Title Buttons: Extra buttons did not react on right clicks in Foxit Reader.[-] Title Buttons: Detecting free place for extra buttons stopped working in Google Chrome in high DPI resolutions since its version 67.[-] Move to Monitor: After moving a maximized Google Chrome window to a monitor with a different DPI resolution, the window got beyond the visible desktop area.----------------------------------------------------------------------------Actual Multiple Monitors 8.12.2 (21.05.2018)----------------------------------------------------------------------------[!] Windows 10 Spring Creators Update: Metro/UWP apps crashed at startup when Actual Multiple Monitors was running.[*] Windows 10 Spring Creators Update, Actual Taskbar: Taskbars now support the new acrylic transparency visual effect.[*] Actual Taskbar, Windows 10: Flyout window with additional notification area icons now looks more similar to the one in the system taskbar.[-] Windows 10 Spring Creators Update, Title Buttons: In some cases, extra buttons got invisible in some