Tier Nine has deep experience in managing software projects. We understand that each project has it’s own set of unique factors. The key to success is to understand each project’s unique set of characteristics, and then manage that based upon time-proven processes which are supported by guiding principles and methodology.
When people talk about their approach to managing software projects, the topic of methodology is also typically discussed. From a project management standpoint, we can discuss different methods and variants, but they basic processes and principle we use when managing a project remain the same.
The most important factor on all of our software projects are people. To enable success we need the right people with the right skill-set and level of experience. This changes over the course of the life cycle of the project, thus process the process of managing resources is continuous. We don’t want to over-staff or under-staff projects. We want the best mix skill-sets, experience, strengths and weaknesses to provide you with industrial strength capabilities at the best blended rate.
Risk means uncertainty, and this is perhaps the most critical success factor on any project. We strive to anticipate risks; evaluate their probability and potential impact, and then re-mediate the risk to decrease any negative impacts to achieving success.
Schedule and Time Line Management
Managing the schedule and time line is another process which we manage vigorously. In today’s market, it’s all about time to market. Deploying your software product later than expected, can be the difference between business success and failure. So many projects are delivered late. This is why we manage delays with very high priority. We also use our experience to modify factors, as they arise, to decrease delays in the schedule and time line.
The scope of the project needs to be defined and very clear, in order to build a good set of business requirements to support the software product. Across all software projects that fail, the most common factor among them is a weak set of requirements. We seek to constantly clarify requirements, build out use cases and user stories, to keep requirements fresh and valid for your business model.
Defect and Issue Management
This process includes the daily chore of identifying, prioritizing and fixing issues. We call this basic “blocking and tackling” and applies to all software projects.
These are the key processes that our project managers keep focus on daily to enable success.
These processes all need to be managed regardless of whether you are using a Waterfall or Agile Methodology. However, most of our projects today do use either an Agile or Agile variant methodology. Given this, we tend to manage the project into smaller iterations of work, but we still discuss factors like Risk, Schedule and Resources while we manage our projects. For us, Agile is built on top of solid guiding principles, our nine core beliefs and time-proven project management processes.