Tag: software environments

  • Managing Your First Software Project

    The first in a series to help you manage your first software project, written by a thirty-year project management veteran.

    You are an up-and-coming superstar in your company and thus, you’ve been assigned to lead your first software project. Maybe, it is upgrading a financial system package, building a new website, or selecting and implementing a new ERP system. It could be almost anything. While you are a great manager and really know the business, you don’t know how to install or build computer systems. You will obviously have some help, but if you are going to manage the project you need to understand what is going on.

    I’ve been helping managers like you run large software projects for nearly thirty years. In this and a series of related posts, I’ll be sharing my experience and giving you the background you’ll need to manage your own project. This post will be an initial overview and starting point advice. I’ll be adding links to other posts covering specific aspects of managing projects.

  • Software Project Roles
  • Software Environments
  • Conclusion
  • Additional Reference
  • People, Process and Technology

    All projects have a people and process component and in this modern age 99% of them also have a technology component. Your primary role will be to manage and coordinate all three of these components to make the project a success.

    People

    What do I mean by “People”? I mean getting the people in the company to support your project or to at least use the software. Until the androids take over, this will also be the hardest part of the project. People are set in their ways and have their own agendas which may not include the extra work your project will cause.

    Consultants use the term “Change Management” to encompass the people aspects of a project. This usually just boils down to training and communication in most projects. In more complex projects this could include designing new positions, adjusting bonus incentives, layoffs or staffing new offices. Whole books have been written on Change Management and I’ll provide more details in other posts, but for this overview just remember that you can build the best software yet it is worthless if people don’t use it. Let’s use COVID 19 as an example. A revolutionary vaccine with the capability to save millions of lives was developed in record time. Yet, a huge level of effort  had to be expended to convince people to take it. The vaccine was developed in a year, but I’m writing this three years after the vaccine was developed and people are still debating it.

    Process

    What does “Process” entail? This refers to the business aspects of the project, and more simply the business process in which the project is changing. For example, the business process scope could be: financial reporting, customer service, distribution, warranties, etc. Your project will be improving this process in some way and will ultimately increase the business’ profit. In the simplest projects, this involves defining the scope and business case.

    An example of scope would be domestic distribution of customer orders in North America, but not international shipments. This is the area where your project will focus, including a rationale for why you are excluding certain processes. Maybe North American shipments are handled in SAP, while international shipments are handled in a custom system developed by your freight forwarder. If the biggest opportunity lies in North America, it makes sense to simplify by only working on SAP for now. While the international shipments can be addressed in the future by another project.

    The business case is simply what benefits will the business owners get for spending the money on the project. How much will the project cost and how much will profit increase? There are projects, like regulatory compliance, which don’t have a direct impact on profits other than avoiding fines or keeping the owner out of prison, in which case the business case is: to keep the owner out of prison.

    In complex process efforts, the business processes or procedures are being redesigned. The way people will do their work is changing. This involves detailed process modeling, documenting new procedures and redesigning performance metrics.

    Technology

    What is meant by “Technology”? In general, it is the thing being built or modified. This is most often software, but could also be a new COVID-19 vaccine. However, I’ll focus on projects building or modifying software since I don’t know anything about inventing vaccines.

    The computer systems will be referred to as “IT”, “systems”, “software” or “hardware”. You will most likely have help from your information technology (IT) department with much of this work. But you don’t want to be blindly leading the technology aspects, entirely dependent on the IT group. You need a basic understanding of how software is developed and implemented, especially so you understand what the People and Process aspects of the project need to do to support the Technology work.

    I cannot emphasize enough that this is the most important component of the project, this is where value is being added. The People and Process components are the supporting players. Therefore, an efficient project is going to focus on making the software developers as productive as possible. If developers don’t have fingers on keyboards then value isn’t being created. If the new computer system doesn’t work, then all the process changes and training are for naught.

    When IT projects go awry a lot of blame is usually leveled at the developers for sloppy coding or being too slow. This is rarely the case. In most cases it is a systemic issue about how the project was managed. System requirements were late or sloppy. Training was poor or non-existent. Testing was poorly designed. The list goes on, but it boils down to the project manager (e.g. you) didn’t do a good job of feeding the developers what they needed and didn’t manage the supporting People and Process components properly.

    Software Development Life Cycle

    All software projects go through the same basic process: Plan, Analyze, Design, Build, Test, Deploy. There are variations depending on whether you are installing existing software or doing custom development, but the basic process is consistent. You will only be performing the Plan Phase once but you’ll be repeating the other phases for each release. I’ll create a post on the details of each of these phases but here is a summary.

    Plan

    The Plan Phase is pretty obvious, you are planning the project and making high-level directional decisions before performing detailed analysis. Some of the key decisions are:

    Analyze

    The Analyze Phase for the first release on large projects can take several months, especially if you have to select the off-the-shelf software you want to purchase. For small projects doing custom coding or using existing software this phase can be only a couple of weeks. The key deliverables for the Analyze Phase are:

    Design

    The Design Phase is focused on software design. All the business and process design work has already been done in the Analyze Phase. The phase is extremely short for small projects making changes to existing software. Software development is so quick these days, it is often easier to build something and review it for input rather than spending a ton of time designing it. If you are building from scratch on a large project the main deliverables are:

    Build

    The Build Phase is the fun phase. The team actually starts building custom software or configuring off-the-shelf software. The Agile software methodology is applied in this phase to build the software quickly and efficiently. You should assume you will be using the Agile approach, as this is the de facto approach for all modern software projects. As manager of the project, you should expect to see working software coming out of you systems development team daily with formal demos every two weeks.

    Test

    The Test Phase should overlap with the Build Phase and wrap up with formal user acceptance testing. As soon as something is built it should be tested by the person who wrote the requirement. So this level of testing should be an ongoing real-time process within the team. Once the build is complete for the release, you should hold formal user acceptance tests with the end users to make sure all the requirements were understood properly. Once end users can get their hands on the software they will always come up with new requirements or bugs. It will be your job to decide whether these new requirements or bugs must be addressed for the first release or can be pushed to a later release.

    Deploy

    The Deploy Phase covers all the activities required to put the software into use. Key deliverables are:

    If your project has multiple releases, you now repeat the Analyze, Design, Build, Test and Deploy phases for the next release. To be efficient, phases for each release should overlap. Business Analysts should start analysis for release two during the Design Phase of release one. Developers should be building release two during the Test Phase of release one.

    Software Project Roles

    Hundreds of people can work on a large software project, and the various responsibilities can be numerous but they basically boil down to a few key roles. Here is an overview of these key roles:

    Software Environments

    A key concept that managers struggle with on their first software project are the many software environments. Think of the environments as different snapshots of the software in time. Different companies use different names but they typically all use four environments for the same functions:

    Some key environment concepts you need to understand as manager of the project are:

    Conclusion

    I’ve given you an overview of the key subject areas for managing a software project. Of course, we’ve just scratched the surface. I’ll be adding more posts on these various subjects to flush out some of the details. Remember your role will be representing the business and ensuring the project goals are achieved. If you assemble a good team, you’ll have the help you need to execute the details correctly. But hopefully I’ve armed you with a enough so you can speak a common language with your expert teammates.

    Additional Reference

    Project Charter Guide and Free Templates

    Save Time with Free Excel Software Decision Matrix

    Receive Project Management Updates

    Get email updates on blog posts and software reviews. I try to write at least one blog post a week.

    Subscribe