Understand What An Infrastructure Project Is
August 9, 2008 | Author: PM Hut | Filed under: Miscellaneous
Understand What An Infrastructure Project Is (#1 in the series Practical Best Practices for Infrastructure Projects)
By Natasha Mocke
In the many years I’ve been consulting as a Lead Technical Consultant, Architect and Engagement Manager there are a number of things I’ve learned from the school of hard knocks. Many things are obvious, and some less so. We can often find methodologies and material about how to run projects effectively, but rarely have I seen anything that discusses infrastructure design and implementation that includes information about how customers and consulting organizations can work together more effectively. This is a rather troubling situation, as many large enterprises work with external organizations to get projects delivered.
In this series I’ll discuss some of the main areas of concern I encounter in trying to enable my customers to operate projects more effectively. I’m focusing on the practical issues I encounter, rather than rehashing project management disciplines and methodologies.
The term infrastructure project sounds obvious doesn’t it, but most of the time it simply is not so. When I speak to customers, and even my peers, at the company I work for an Infrastructure project is usually some kind of storage, file and print, OS deployment, software distribution or messaging project.
Rarely do people consider that infrastructure, more often than not, provides the non-functional elements of an application development project. Some of my customers get it right, but most do not. Developers are not infrastructure people. They are more concerned with making it work, rather than being focused on redundancy, high-availability or operational environments. And rightly so! The problem is many people expect that developers can run SETUP and get things going, so they don’t bother initiating an infrastructure project or sub-project in application development projects. This often leads to fantastic application development work not translating to success because the infrastructure belt and braces are simply not there to deploy and run the application successfully.
Natasha is a Pre-Sales Architect for Infrastructure and Business Productivity applications and systems. She has worked at a major software vendor for more than 10 years, in a number of consulting and delivery management positions, including Service Line Architect for a period of 4 years. She has more than 18 years of experience working with her customers to design and implement solutions in these areas and is primarily focussed on security, virtualization, messaging and management architectures. She is a Microsoft Certified Architect: Infrastructure, and was one of the first Microsoft Certified System Engineers in the world.
Related Articles
No comments yet.
feel free to leave a comment
Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!
XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
All fields marked with " * " are required.










