Lessons Learned Going Into 2010

by E.R. Williams

With "Recovery" on everyone's mind, RayAnn thought it would be appropriate to share some lessons learned going into 2010.

  1. Document all planned steps/actions in the web development process with input from key stakeholders and project team members.
  2. Never rely strictly on a WYSIWYG application (I.E. Macromedia Dreamweaver, Microsoft FrontPage) to complete a web design/development project.
  3. Ensure that all proposals are understood by all involved parties and a complete needs analysis has been performed before signatures are granted.
  4. Reduce the high risk in projects and programs by identifying, defining, and understanding business and system/product requirements.
  5. For 2010, ensure that best practice processes and best/good practice activities are identified and included in the development process.
  6. Establish from the beginning a mechanism for project and process improvement.
  7. Again, understand that configuration management is about, and essential to, successful project management control and quality.
  8. Project management is essential (and more important than many realized) for any industry
  9. Continue to understand the importance of a communication and risk management plans for local and virtual projects.
  10. Realize that companies that focus on people and process contribute directly to the project/program's success and increase in revenue and profits.
  11. Prepare for more global projects and realize individuals will be relocating to do international business (But is there a difference when they come here and we go there? See February's Newsletter a Program/Project Manager's perspective)
  12. Build a base of skills in other areas beside your primary skills set/competency (e.g., management, technology knowledge or technology, management and business knowledge)
  13. Avoid scope creep by addressing (cost, contract impact and analysis), documenting activities/tasks before they are added to a project or program after the project or program is being executed
  14. Requirements are stable, consistent and comprehensive when the customer, user, and contractor are involved from the beginning to define and mutually agree/approved requirements. Requirements are essential to a successful project and the bridge to full scale development. When using an Agile development process or method ensure the each sprint/functional release has complete requirements (may change but through a controlled process).
  15. The network and infrastructure must be stable to except any functionality introduced into it, and validate that it is for any change that is introduced into the environment.
  16. Resource management must result in having the right people, skill sets and communication skills for domestic/national and international/global projects and programs for a diverse team and in a variety of cultural environments.
  17. Doing business now and in the past should be, and should have been, about building relationships/partnerships. It's still about being customer and team focused with the customer and users involved. It's about having a long term business relationship, not, "I don't know what we are going to do when this contract is over".

Previous post:

Next post: