Resource Library

Anyone who’s managed switches over the years knows that the Spanning-tree protocol (STP) is both the best and worst thing to ever happen to the data center at layer 2 of the OSI model. On the plus side, the Spanning-tree protocol is what first allowed us to create redundant paths within our switching infrastructure, making our data center much more resilient to outages than ever before. Anyone who’s experienced a “broadcast storm” knows the full value of Spanning-tree in the traditional switching environment. We’ve also seen many improvements in Spanning-tree over the years to make it work faster and more efficiently (i.e. Rapid Spanning-tree, Bridge Assurance, and many others).

Instructor Carol Kavalla talks about the advantages of taking a Cisco Data Center Unified Fabric Implementation class from Global Knowledge.

Business processes are complicated, and mapping them is not a trivial task. Modelling standards give us the tools to model complex processes, but they do not tell us the best way to approach a model or effectively use the tool. In this hour-long webinar, Global Knowledge instructor Rod Fage will guide you through the best way to develop a model, from determining the goal and scope of the process and measuring its effectiveness, to modelling the process in a hierarchical top-down approach, enabling business analyst to continuously validate the model.

I attended a meeting this week with a customer of mine and a potential new vendor. The new vendor was there to pitch his configuration and setup service offerings for a specific ITSM toolset. My customer has already had one bad experience with an ITSM tool configuration vendor who promised one thing and delivered much less. He ended up with a tool that’s minimally used and not configured to match his business needs. He’s looking for a vendor that can understand his business needs and priorities and quickly help him get his tool configured and working in a short time frame. Then the topic of standard changes came up. My customer asked for examples of standard changes. The vendor responded, “Server reboots are an example of standard changes.”

Resource management is always an issue in any project, especially when the stakeholders from whom we need time have operational duties to perform.  If our requirements team was at our disposal 100 percent, always completed activities on target, and worked a full eight hour day without distraction or a loss of productivity, then estimating time would be simple. In this paper, we explore standard approaches to time estimation, the dangers of multi-tasking, and estimation alternatives, which consider work habits and productivity norms.