Industry and subject matter experts believe that we are in the early stages of an era of technological advancement that will dwarf the Internet era of the mid to late 90s. Having a basic understanding of these technologies and their current status will provide program and project managers with the tools they need to move forward.
This series focuses on preparing you to embark on your transformation journey and help you ask the right questions, understand and accept facts, define realistic goals and consider the right parameters. Most importantly, it helps you establish continuity and sustain such strategies in the long term. The first installment helps you ask the right questions and accept facts.
Agile is all about managing change, but every organization has a different rate of change. We generally think about agile as removing impediments to accelerate development and keep up with change. It also has an important role to play in placing constraints on change so that it doesn’t spin out of control. This article is a case study of how too much change can lower quality and lead to products that completely miss the mark.
Selection of the correct process technology for a manufacturing industry, with several complex variables that will dictate success, is of vital importance. This article applies Analytical Hierarchy Process (AHP) to complex problems with both objective and subjective criteria. Here, the methodology is used in a selection decision for identifying the optimal technology for a steel-making enterprise.
The Titanic was an ambitious project, projected to reach extraordinary success...but it sank. Why did this happen? By going through this interesting historical case, we'll visualize how behavioral aspects could sink the best project or business. These are “must have” concepts for any manager interested in getting the most from projects.
Question: I’m not in IT, but I’m heading a project to implement one of those big name software packages that is supposed to place all the corporate information in one application. We’ve rolled it out, but as a 24-hour organization it seems that we have departments unable to access their information at all hours of the day and night. Our vendor is on call for the fixes, but the outages interrupt our business. I’m discouraged, angry and exhausted. How do I manage these issues?
With a big name supplier, the responsibility to keep things up and going is on their shoulders, not yours. Contact upper management and ask to have any payments to them stopped until all areas of your organization are up and running with no down time for at least six weeks.
Each department was probably given a chance to express what connectivity they needed before the customization of this overriding package was finalized. Get the name of each person who was part of the planning team and subsequently had an outage in their area and report them to their own manager.
Ask your own IT team to get involved in solving these issues. Obviously, the vendor does not have competent people on its staff who can manage an install like yours. If your own internal staff takes over the responsibility, you will have better communication and a team that understands the high stakes when your systems go down.
The reality of any install that must switch over an entire organization at one time is that there are going to be hiccups. But as a non-IT expert, the most productive path for you is to create a way that the failures can be grouped and tracked so that past problems can be easily accessed to provide faster solutions to new outages or feature failures that occur.
This series provides valuable information for the product owner community to use additional good practices in their projects. In each installment in this series, we take one of the most commonly used visual models in agile and explain how to create one and how to use one to help build, groom or elaborate your agile backlog. This installment looks at business data diagrams.
Despite the poor success rates reported in 2015 in using Big Data and data analytics, it appears that for 2016 and beyond, they are on their way to being a massive market. What are your organization’s plans for pursuing these initiatives?
In the world of IT, each project comes with a different set of expectations and requirements that make everyone nervous about estimating cost, time and level of effort. Estimations based on a mature estimation model (function points) are more likely to be successful than projects that are estimated ad hoc, based on expert judgment alone. Function points translate all project functionalities into equivalent efforts. Combined with a well-defined process, they serve as a powerful tool for accurate estimations.
Stories of many failed Big Data projects have cast doubts on their strategic necessity and value. This raises the question of whether Big Data analytics and the associated technologies are a strategic disruption for organizational productivity, or just another hyped-up pretender of business value—a storm in a business teacup?
Question: Ah, the dreaded new boss! This organization works through other vendors to deliver our international training services. My team reviews them for longevity, education and certification of instructors, stability of organizational structure, quality and content of their materials, publicity and webpage honesty, and similar traits found in a high-value partner. The new boss has no background or understanding of our industry or training in general, and immediately wants to impose strict metrics to evaluate my team and me. This doesn’t seem like a good idea. Am I missing something?
Metrics or concrete, short-term data about the performance of each person working for an organization are crucial to make sure that team members are not slacking off and occupying a position someone else could use to bring the company more value.
The new boss is trying to make his or her mark by introducing the new metrics to have something concrete to show. These statistics will prove to not be a good idea over time, so let the organization figure it out for itself. Collecting them is the equivalent of the lion’s roar to mark this territory to all within earshot.
Only people who are fearful of what the data will show will object to having it collected, formed into charts and submitted to management. In fact, since you know what is being gathered you can change your daily performance to be sure you look good in these new metrics regardless of whether or not it is the best use of your time.
An organization should look at the need for and value received from any metrics gathered and used. Unless they are collecting data that is meaningful and will lead to better results, they are a waste of company time and resources, may be misleading and may be discouraging for the team.
Question: There is good news and bad news! I have been asked to head the largest project of my career—that’s the good part. The bad part—it’s about knowledge management. Of course I know in general terms what that means, but somehow with the budget and size of the team I’ve been assigned, I think they are expecting a much broader scope that I may have anticipated. How can I get a quick update of the latest version of the extent of this generic term?
This can mean many different things within an organization. Update yourself with some quick reading, then check with the project sponsor or business analyst to make sure you aren’t including or leaving anything out of the scope that management is expecting.
Ask your team to see if any of them have encountered this term in past jobs or in a user group setting. Don’t be afraid to let them fill you in on what this means in today’s terms, especially if they are young.
Check at your local community college or with national training vendors to see if they have a two-day class on this topic. If a project manager like you has questions, there must be many other people in your area who need the same information.
Ask the Project Management Office (PMO) in your organization to have the training department conduct a training session for you and your team so that everyone has the same information. In that way you can learn about it yourself without having to expose your current lack of knowledge.
How do you select the best data extraction/transformation toolset for your data warehouse? Evaluate features, functionality, vendor reputation... the works. Follow the example set by this robust tool evaluation.
Even though you've built the perfect data warehouse, it's better to be safe than sorry if something goes wrong during its operation and you need to restore the original data files. Take the time to document your backup and recovery procedures, as in this example.
Mission-critical projects need to be well-justified, with clear goals that can be referenced throughout the life of the project. This business case template offers an excellent approach to goal-setting and a way to communicate those goals effectively.
Code is a developer's signature on a software project, and not all developers play by the rules of good coding standards. Ensure that your development team leaves a coding legacy that not only implements the application at hand but can be understood by others and maintained during future development cycles.
Are you putting together a data warehouse? This Microsoft Project plan will help you keep tabs on all the complex stages and steps involved in building decision support systems and a knowledge-based applications architecture and environment.