Typical project management challenges

RequirementOne helps project teams around the world manage their projects including user needs, requirements, use cases, tests, tasks and most other day to day activities that are required to run a successful project.

We are very focused on the needs of our users and we encourage feedback and discussion of all the challenges that our community experiences. Through this dialogue we have identified typical challenges that are common throughout our user base and this article will outline how to deal with these challenges and explain how they relate to the execution of a successful project.

Challenge: The biggest challenge is really ensuring consistency amongst the different individuals involved in the project process, and not seeing differences between the specspecification, the wireframes and the designs.

RequirementOne: The requirement specification(s) that contains the user cases, business requirements and functional requirements should be the single source of truth for what needs to be delivered. Wireframes, mockups and other design documentation are derived from this documentation.

Challenge: There is a need to keep detailed and accurate records of decisions made by the project team about different aspects of the project and being able to refer back to previous versions so we you don’t end up repeating the same discussions.

RequirementOne: From a strict project management point of view decisions related to product functionality will always relate to:

  1. new requirements
  2. changes to existing requirements
  3. issue fixing (a requirement that has not been implemented correctly)
  4. and how the implementation of these are is prioritized and assigned to future releases.

Challenge: Problems caused by completing tasks in the wrong order

RequirementOne: This should be managed by assigning priorities to individual requirements and issues which in turn should be assigned to a given release containing a specific set of requirements and issues. The methodology used for your release planning will vary depending on your project environment which would typically be either agile or waterfall.

Challenge: Underestimating the amount of time needed for some areas.

RequirementOne: Estimation is typically always difficult to get right but the more detailed your requirements are the easier it is to “guess” right. Typically it is a good idea to break down your estimates in to the different activities required e.g. implementation, test and project management.

Challenge: In short, we have some great experience and some useful tools but we lack consistency of approach and clarity of the task ahead amongst the whole team.

RequirementOne: The consistency will come from getting better procedures in place and introducing a centralized project management platform like RequirementOne that manages project plans, requirements and issues. You can also if you choose to register issues in a separate system but then you will not get the benefit of being able to hyperlink issues to requirements and have everything stored in a single system.