Tag Archive for Management

Stop Having These Meetings

Stop Having These MeetingsFollowers of the Bach Seat know that passwords suck. As a Project Manager, something that also sucks are bad meetings. Meetings that don’t have an agenda or a goal or a purpose will suck the motivation out of people coming to the meeting. In the interest of having fewer sucky meetings here are some meetings, your team will thank you for eliminating or fixing.

The Monday morning staff meeting

Monday Morning Staff MeetingsThe problem with this meeting is that no one is ever ready for it. After all, it’s 8:00 a.m. on Monday morning. Nothing has happened yet and whatever happened last week is mostly ancient history. A second problem with this meeting is that for anyone to be ready, they have to work Sunday night. That is fine on occasion but guaranteed to earn you some serious votes for “jerk of the year” from employees and the family members of employees. For a while, I worked for an insomniac boss who would fire off emails off at 2:00 AM on Sunday. She would expect answers at 8:00 AM meetings. It was a happy day when she moved on.

The third problem with this meeting is that stuff happens on the weekends. And stuff needs to be addressed, especially in IT. Did you change your tapes? Check your logs? Walk your data center? Are there warning lights? How many tickets are there? Who has time for a meeting? The solution: if you must run a team meeting on Monday, push it to later in the morning or early in the afternoon. Better yet, push it to Tuesday morning.

The Round-the-Table status meeting

Round-the-Table Status MeetingWe have all been there. It’s the meeting where focus moves around the room and everybody shares their latest updates, sagas, fantasies, and dreams. Sit in the wrong place and you end up as the 19th person to offer an update. By that time nobody cares because their bladders are over-strained and brains numb from the politically oriented updates emanating from the mouths of colleagues in far-away functions.

The solution: meet if you must, but set some rules on the updates. Ask people to focus on important news that impacts everyone or on challenges that need help from across functions. Do anything to limit the painful march of gratuitous and self-serving status updates that undisciplined round-the-table meetings generate.

Recurring meetings with no purpose

Recurring Meetings that Have Lost Their PurposeAny recurring meeting where no one can remember why this meeting still takes place is a candidate for immediate elimination. The laws of physics transfer to meetings. A meeting on the schedule tends to stay on the schedule long after it has used up its usefulness in the workplace.

The solution: review all the recurring meetings that you subject your team to or that you are a participant in. Drop them from your life and the lives of your team members. If you are not the host of the meeting, tell the host of your intention and of your perspective on the utility of the meeting. If you are the host/sponsor, poll team members and give them a voice and a vote. A bit of draconian slicing of recurring meetings opens up valuable time for other more important activities.

Group wordsmithing

ThGroup Wordsmithing Meetingsis is any meeting where you pull together a group of people to work on the wording for something. Be it a vision, a mission, a strategy statement, a scope statement in project management. The output of these sessions is typically a series of awkwardly constructed sentences reflecting compromises on the part of the HPPiO. Everyone nods their heads, yes but no one agrees with the final product. The wording moves beyond ridiculous to just awful in trying to make the pain go away.

The solution: never relegate rough wording of anything to a committee. Take a stab at the item in question yourself. Then bounce it off a few colleagues. When you approach something that is beginning to work for you, very carefully ask for comments from a group. Ask clarifying questions, take great notes and then disappear and redraft the statement(s). Repeat the process as necessary.

Death by PowerPoint

Death by PowerPointDeath by PowerPoint is a phenomenon that can make any meeting suck. The poor use of presentation software causes Death by PowerPoint (DBPP) according to TargetTech. Key contributors to DBPP include confusing graphics, slides with too much text, and presenters whose idea of a good presentation is to read 40 slides out loud.

Audiences that are emotionally disconnected from the presentation are the fault of the presenter. There is a good chance that the speaker has not spent enough time and effort thinking about which key points he wants the audience to take away. Or she has spent entirely too much time and effort setting up the presentation in PowerPoint.

DBPP can be avoided if the speaker uses the technology as a visual aid to enhance what is being said. Do not rely on the technology to serve as the focus of the presentation. Don McMillan demonstrates what not to do with PowerPoint in his video “Life after Death by PowerPoint.”

How to be better at meetings

Meetings are opportunities ripe for overuse and even abuse. Strive to be the manager that respects the power and importance of meetings. Use these forums to focus on key issues and solicit ideas. To keep your meetings constructive you need to start with respect.

Respect the time that everyone puts into the sessions. Start your meetings on time. If your meeting starts on time there are fewer chances to derail others’ productivity throughout the day. Starting on time also helps you to end on time. This is crucial because once the time slot for the meeting is over, employees will start to mentally check out whether you’ve made it through the agenda.

rb-

Bad meetings suck so much that the Project Management Institute (PMI) added a section to the Project Management Book of Knowledge (PMBOK) on meetings. that right – In version 5 of the PMBOK Integration Knowledge Area, there are four processes that have “Meetings” as a Tool & Techniques.

  • 4.3 Direct and Manage Project Work
  • 4.4 Monitor and Control Project Work
  • 4.5 Perform Integrated Change Control
  • 4.6 Close Project or Phase
Related articles

 

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.

2015’s Worst Passwords

2015's Worst PasswordsFollowers of Bach Seat know that passwords suck. For even more proof that passwords suck, the password-management company SplashData released its fifth annual list of the most popular passwords. SplashData studied more than 2 million passwords that were leaked in 2015 and identified the most commonly leaked passwords and those that were least secure from Western European and North American users according to Business Insider.

2015’s worst passwords

SplashData logoMost of the 2015 results are not surprising.

  • 123456 is the most common password. It has been #1 since 2013.
  • Password is the second most common password. It too has been #2 since 2013. Password was the most common password in 2012 and 2011.
  • 12345678 is the third most common password found in the Splash data results. In fact, 12345678 has been the most consistent performer, having been in the #3 place four of the past five years.

One surprise was that the Disney marketing machine was able to get Star Wars related terms into the top 25 worst passwords in 2015.

  1. princess
  2. solo
  3. starwars

Here’s SplashData’s full list. If your password is on here, think about changing it.

25 Worst passwords

20152014201320122011
1123456123456
123456
password
password
2passwordpasswordpassword123456
123456
3123456781234512345678
12345678
12345678
4qwerty12345678
qwerty
1234
qwerty
512345qwertyabc123qwertyabc123
612345678912345678912345678912345
monkey
7football1234
111111dragon
1234567
81234baseball
1234567pussy
letmein
91234567dragoniloveyou
baseball
trustno1
10baseballfootballadobe123
football
dragon
11welcome1234567123123
letmein
baseball
121234567890 monkey
admin
monkey
111111
13abc123letmein
1234567890
696969
iloveyou
14111111abc123
letmeinabc123
master
151qaz2wsx111111photoshopmustang
sunshine
16dragonmustang1234michaelashley
17masteraccessmonkey
shadow
bailey
18monkeyshadow
shadowmasterpassw0rd
19letmeinmastersunshinejennifer
shadow
20loginmichael
12345
111111
123123
21princesssupermanpassword1
2000
654321
22qwertyuiop696969princessjordansuperman
23solo123123azertysupermanqazwsx
24passw0rdbatmantrustno1harleymichael
25starwarstrustno10000001234567football

 

Protect yourself

keep your passwords secureTo keep your passwords secure, you definitely shouldn’t use any of the passwords on the list.

SplashData offers three simple tips to help people protect themselves:

  1. Use passwords or passphrases of twelve characters or more with mixed types of characters;
  2. Avoid using the same password over and over on different websites
  3. Use a password manager such as SplashID to organize and protect passwords, generate random passwords, and automatically log into websites.

rb-

What to do if you are responsible for securing systems where your users use these passwords? Stop Them!

This is what makes passwords suck – Implement complexity rules:

  • Minimum of 8 characters
  • A mix of characters, UPPER CASE, lower case, numbers, and special characters.
  • Prevent reusing passwords
  • Blacklist all the above passwords so they can never be used again.
Related articles

 

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.

4 Tips for Dealing with IT Sales People

Tips for Dealing with IT Sales PeopleJonathan Feldman penned an article for InformationWeek which provided some tips on how to deal with vendor sales people. The Ashville NC, CIO writes that most IT pros think doing calls and meetings with vendors are a waste of time. However, he states that IT vendor salespeople have a place in the IT ecosystem. The author argues salespeople can be a benefit;

… if you stick your head in the sand, stick your head in the sanddon’t be surprised when you fail to move forward … We all know the bad side of sales. But the good side, at the correct time and in the correct dosage, can usher in business technology innovation.

The article explains it’s all about sound vendor management. Mr. Feldman describes four things he does to ensure that time with the vendor is as productive as possible for him.

Establish guidelines for sales people

TEstablish guidelineshere should be a process for vendor meetings. Mr. Feldman says that staff should know what to do when faced with a vendor on the phone, or worse yet (which I’ve seen) at the front desk.

  1. Should they take the call immediately?
  2. Pass it to someone else? If so, to whom?
  3. If it’s decided not to engage the vendor at all, based on what criteria?

Any way you slice it, staff need guidance so that they don’t go overboard one way or another.

Set expectations

Set expectationsProvide vendors a mechanism for contacting you. CIO Feldman suggests the website should clearly state where product and service calls should go. He also suggests that voice mail announcements spell out a number that vendors should call if they want assistance.

This is an early test of vendors if they can follow your directions. If they can’t properly get in touch at the beginning, how are they going to behave at crunch time? rb- I use the same logic at RFP time, vendors certainly raise a flag if they don’t read the directions and respond in the requested format.

Direct the call

Limit cold callsIt is your time, do you want to spend it on a cold call? I have found that cold calls are rarely useful. Mr. Feldman suggests you limit cold calls to five minutes, tops. He makes the vendor get right to the elevator pitch to quickly check whether to hear more at another time. To cut through the chaff, he recommends a question like, “What’s the value in what you’re selling, in 30 seconds or less?” Hang up on people who say they’re not selling anything.

Control timing

If the salesperson has followed the process and made an appointment and showed up (rb- a problem for first time calls or small accounts) keep the meeting short. The author says these early meetings should be less than 30 minutes to hear and evaluate their message. These calls are to evaluate the elevator pitch, not to discuss strategy. Control the timing; don’t let it control you.

Evaluate the elevator pitchMr. Feldman concludes that ignoring sales calls isn’t an option unless you want to join the legions of the uninformed. He recommends that IT Pros sift through the sales noise to decide which pitches merit action to benefit your business.

rb-

I have managed the vendor pitch process by having quarterly pitch Fridays where new vendors could get 30 minutes to pitch their business. This allowed us to schedule the meetings around our customer’s work. And it made it easy for the admin staff to schedule, here is your time like or lump it. And it pushed the meeting out enough to test sales commitment.

Related articles

 

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.

Wiring Closet 3.0

Wiring Closet 3.0The lowly wiring closet at the edge of the network is evolving. You know the one’s that IT shares with the custodians or the women’s lav. The neglected place that connects all end-points into the enterprise network infrastructure. Throughout my career we have moved from 3Com SuperStack hubs to 10/100 SuperStack switches to 100/1000/10000 Cisco 2960’a fixed Ethernet devices. In this first edge era, the primary buying criteria was the price per port. Low price was the critical factor. These devices might have had a few network services but they only provided best-effort connectivity services with little to no operational control according to Nick Lippis in the Lippis Report 103: Wiring Closet Switches Gain Strategic IT Value Label.

Baystack stackCommoditized network gear created enterprise networks consisting of equipment from different vendors. Purchases throughout the wiring closets, distribution, and core were based mainly on cost. The article says that equipment from multiple vendors is the hallmark of Wiring Closet 1.0. Wiring Closet 1.0 made effective management difficult. Multiple management systems required that organizations keep a large staff with diverse skills to keep up network functionality.

Wiring Closet 2.0

Most organizations are now in the Wiring Closet 2.0 era. As competition drove margins on edge switches into the single digits, the author states that vendors began to add services to a new breed of device. The new features on 2.0 switches created new ways for the vendors to compete on different (rb- and more profitable) fronts beyond price per port. Mr. Lippis argues enterprise trends are forcing IT executives to check projects, programs, and priorities as they seek to drive down Total Cost of Ownership (TCO) while extracting added value from their enterprise network. Business executives expect their IT departments to meet continually growing demands without significant year-over-year network expenditures. (rb– the ever popular more with less argument) The article says the new realities include new mixed traffic patterns and increased desktop bandwidth requirements for new applications, communications, and data center strategies.

Goddard rocket scientistSwitch vendors recognized these trends. They responded by developing a new type of wiring closet switch. Second-generation switches added significant functionality. The vendors’ goal is to transform the commoditized network edge (rb- low profit) into a strategic IT asset (rb- high profit). The blog says these new switches enable a host of new applications for Wiring Closet 2.0.

  • Quality of Service: Wiring Closet 2.0 switches tag applications like IP telephony and Unified Communications at access to guarantee priority throughout an internal network and active monitoring
  • Power Over Ethernet (PoE): Second generation, wiring closets distribute power over Ethernet cables. POE enables new classes of devices to be powered from the Wiring Closet 2.0. These demands include WLAN access points, video surveillance, and IP phones. As well as specialty devices such as health care instrumentation, point of sale devices and soon even laptops.
  • Security: The network edge Is the first level of defense. Network Access Control (NAC) and application policing have increased in importance. They are needed to protect the integrity of the network, data privacy, and compliance. Wiring Closet 2.0 switches integrate security features and the support of security appliances bolstering defense-in-depth strategies.
  • Wireless Local Area Networking: WLAN integration, which includes access point, PoE, and controller support, increases WLAN coverage. Further common network management interfaces streamline operational support for both wired and wireless networks.
  • Unified Communication (UC): UC support via PoE to power IP phones and UC end-points plus unique UC configuration profiles to ensure reliable and stable UC operation.
  • Application Intelligence: Application intelligence or the categorizing of applications as they enter the wiring closet and either mark them with QoS or discard the application. This enables application policing at the network edge.
  • Layer 3: Full layer 3 forwarding enabling all the value associating with routing including segmentation and aggregation are now included in some wiring closet switches.
  • Total Cost of Ownership: The network edge and wiring closet switches in particular have a TCO breakdown of 20% capital spend and 80% operational spend according to Gartner (IT). Mew wiring closet switches are more expensive from a capital acquisition point of view. However, their operational cost is lower. Thus, the total dollar spend over a three-year period will also be lower while delivering increased value to the enterprise.

Wiring Closet 3.0

The IT industry is on the verge of a new era at the network edge. New technologies and requirements will disrupt Wiring Closet 2.0.

  • 10Gbps Ethernet: 10Gbps Ethernet is the future of networking. If the past is a guide to the future, then over time more and more 1 Gbps Ethernet ports will upgrade to 10 Gbps. This will place a strain on wiring closet packet processing performance while driving up 10Gbps port density requirements plus downstream distribution and core switch capabilities.
  • Software-defined networking (SDN): The holy grail of SDN is to separate the network control plane from the data plane. The model I carry in my head is wireless networks. There is a central controller that tells the WAP’s what to do and they do their job without any help from the central controller. This implies that the network devices can be dumber and cheaper.
  • Network Management: Consistent network management means leveraging the same supplier for the network edge, distribution, and core.
  • True Layer 3 Support: To support all the above-mentioned trends and unforeseen applications, wiring closet switches need to support full layer 3 forwarding.
  • Support of UC, Mobility, and Security: This basis of competition is one of the most important attributes to the new network edge. Wiring closet switches need to support both standard interfaces and services for UC, mobility, and security so that mixed vendor solutions may occur.
  • IPv6: If you have wiring closets full of perfectly good Layer 2 switches, there’s no reason to replace them just because you can’t manage them with IPv6. If they work today, they’ll work until they break, and you don’t need to worry about (or budget for) swapping them out any sooner.

IPv6

IPv6

Dan Campbell, President, Millennia Systems, Inc. suggested in a recent CircleID post that to manage the move to an IPv6 enabled Wiring Closet 3.0. Organizations should strive to use theIPv6 dual-stack migration strategy. This is where IPv6 is added to the existing systems so they can simultaneously function with both IP versions. Tunneling and translation techniques should be used when the dual-protocol configuration is not possible. The mantra of “dual stack where you can, tunnel where you must” is the order of the day.

He advises that starting today, don’t buy another box unless it supports dual-stack operation or offers a clear, well-defined upgrade plan. It doesn’t matter if the manufacturer is “up and to the right” in the latest Gartner (IT) report; anything you buy from now on that is IPv4-only is a waste of valuable resources.

Mr. Campbell tells network administrators that while LAN switches function mainly at layer 2. They forward Ethernet frames regardless of whether the packet inside is IPv4 or IPv6. There are some functions on a switch that works at layer 3 or higher. They include:

• Dynamic ARP Inspection (DAI).
• DHCP Snooping.
• Multicast Listener Discovery (MLD) Snooping (the IPv6 equivalent of IGMP Snooping).
• Quality of Service (QoS) marking for upstream Differentiated Services treatment.
• Access Lists (e.g., VLAN or regular ACLs).

He explains that these features need layer 3 or upper-layer information; Layer 3 is needed to inspect the packet header or payload inside the Ethernet frame. These features may not be things you are doing now, but you never know when you will. Security requirements and hardening guidelines are recommending things like DAI, DHCP Snooping, and ACLs at the access layer.

The more streaming video gets moved to IP networks, the more the need for multicast. MLD Snooping is necessary to improve performance. Finally, the continued convergence of voice, video, and other rich media and interactive applications to IP networks is furthering the need for QoS. It is always best to mark traffic as close to the edge as possible.

Related articles

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.

Project Managers Grow in Importance

Project Managers Grow in ImportanceIn a recent post, Computer Economics has found that the slowdown in capital spending has been good for project managers. With fewer projects and thus fewer project managers, Project managers are growing in importance. Project managers with sound project management become even more important when projects are downsized, delayed, or outsourced.

Their study, Project Manager Staffing Ratios, finds that over a five-year period project managers have risen as a percentage of the IT staff. In 2011, project managers made up an average of 4.5% of the IT staff, up from 3.4% in 2008.

Project Managers Grow in Importance

The ratio rose sharply in 2009 to 4.3%, indicating the recession played a role. While IT organizations were reducing headcount, project managers fared better than most other IT job functions according to Computer Economics. The ratio has remained relatively steady over the past three years, peaking at 4.7% in 2010.

The author summarizes that IT organizations are relying more and more on professional project managers. The reasons for this growth are varied. They include new technology adoption, regulatory compliance issues, and outsourcing. There is also the ever-present mandate to do more with less. All of which contribute to the need for project management.

Perhaps the most pressing reason for the growth in project management staff is that many organizations have a poor record of bringing IT projects in on time and within budget according to the article. Much of the work in IT organizations today is project-based. IT managers are beginning to realize that project management is a critical element in delivering successful projects. And value—to the business.

Related articles

 

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.