Bill Clinton famously said "It depends on what the meaning of the word 'is' is. " Where his point was the tense of the word meant 'is' it happening currently, not same meaning as 'was' something happen several years ago.
When it come to communication words have the meaning we give them, so it all depends on your definition. This is why in an IT project we have a data definition library but its often the common everyday words that can cause the most trouble, if not defined.
Example 1:
Jack: Are you using the your server slice.
Jill: Yes.
Jack: Are you using the your server slice Today.
Jill: No.
In Example 1, Jack wants to use Jill's Server Slice to do some work right now, however, Jack never says that, so Jill thinks Jack is trying to get ride Slices that will never be used. Difference being: can I 'have' the that slice VS can I 'borrow' that slice. Yes, this conversation actually happened:)
Example 2:
Jill: We can not use this tool because its not enterprise.
Jack: What's your definition of enterprise?
Jill: The tool doesn't say its enterprise.
Jack: I could contact the developer and ask to add the word 'enterprise' to the tool's description.
Jill: I see, we need better criteria. It needs to be supported and recommend by Salesforce.
Jack: Well, here is a recommendation on the Salesforce wiki. Now what's your definition for support? Do you mean online documentation like on the tools website?
In Example 2 Jack has recommended a tool to auto load files into salesforce. Jack is really trying to understand Jill's definitions by both offering suggestions and asking questions for criteria to understand the root cause. Also note that Jack 'accepts' the definition given by Jill and never 'tells' Jill its a poor definition or 'dumb idea'. Jill quickly realized that the definition of enterprise needed to be more then just a keyword and came up with real criteria that added value and minimized the risk of using the tool. Enterprise companies should always have criteria for evaluating a software program and tools they uses so they can compare the options when making a decision.
Showing posts with label project. Show all posts
Showing posts with label project. Show all posts
Wednesday, April 23, 2014
Monday, June 3, 2013
Why Cloud isn't used for IT projects?
Traditionally making changes to software requires a tedious process of waiting on the IT depart to make any seaming little change. We in IT no that even the smallest change requires impact analyst. However, with Cloud based software like Facebook, SalesForce, LinkedIn, Google, and more, the IT department doesn't need to maintain and ignores the software.
For example, Marketer may be able to update the companies Facebook page with no help for the IT department; as a result the IT department is not kept in the loop as to what happens on Facebook. Therefor the Cloud Admin works in a silo without creating system documentation, collaborating with other IT, or being included in the companies current and future Roadmap plans.
Similarly SalesForce or other Clouds that could be used for company wide IT projects are seen as managed by the users; and therefor not considered or more importantly evaluated by the IT department. By being too easy for the user to use, the IT department does not need to be involved with the software, and therefor focuses on software that requires their attention. This results in a lack of interest and skill on the unfamiliar cloud & ultimately limits its use and growth to what the user can do on their own with what ever free time they have to do it. Further more, the cloud software admin is usually doing jobs so the time spent on changes is rushed instead of thought out for impact analyst.
Like it of not, the new Cloud admins may be part time with primary job as a Marketer, Coordinator, Administrative Assistant, or other. This means they are part of the IT department and should be included in the IT discussions for future company wide IT projects, and Cloud platforms considered as useful tools. The IT department doesn't need to learn how to develop in every platform as most of these don't require maintenance and you can always find a temporary contractor to find to do the work. Like with Agile development its the collaboration and impact analyst that is most important to the successful implementation of any project.
For example, Marketer may be able to update the companies Facebook page with no help for the IT department; as a result the IT department is not kept in the loop as to what happens on Facebook. Therefor the Cloud Admin works in a silo without creating system documentation, collaborating with other IT, or being included in the companies current and future Roadmap plans.
Similarly SalesForce or other Clouds that could be used for company wide IT projects are seen as managed by the users; and therefor not considered or more importantly evaluated by the IT department. By being too easy for the user to use, the IT department does not need to be involved with the software, and therefor focuses on software that requires their attention. This results in a lack of interest and skill on the unfamiliar cloud & ultimately limits its use and growth to what the user can do on their own with what ever free time they have to do it. Further more, the cloud software admin is usually doing jobs so the time spent on changes is rushed instead of thought out for impact analyst.
Like it of not, the new Cloud admins may be part time with primary job as a Marketer, Coordinator, Administrative Assistant, or other. This means they are part of the IT department and should be included in the IT discussions for future company wide IT projects, and Cloud platforms considered as useful tools. The IT department doesn't need to learn how to develop in every platform as most of these don't require maintenance and you can always find a temporary contractor to find to do the work. Like with Agile development its the collaboration and impact analyst that is most important to the successful implementation of any project.
Subscribe to:
Posts (Atom)