Category: Configuration Management

  • A restatement about lessons learned…

    RayAnn received another several emails recently but they were questions that you would have thought were part of the past. The emails indicated that the managers were documenting lessons learned and having a end-of- the-project meeting to discuss lessons that were only gathered after or during the last phase of the project. Unbelievable! Hear is…

  • Have a proactive attitude when it comes to your project or program.

    When implementing technology in any environment you have to consider several best practice activities for the following items, early and continuous: Training and education that have to be provided Communication planning (a plan that has to be prepared and executed) Risk management planning and management ( a plan that has be prepared and addressed throughout…

  • Lessons Learned Going Into 2010

    With “Recovery” on everyone’s mind, RayAnn thought it would be appropriate to share some lessons learned going into 2010. Document all planned steps/actions in the web development process with input from key stakeholders and project team members. Never rely strictly on a WYSIWYG application (I.E. Macromedia Dreamweaver, Microsoft FrontPage) to complete a web design/development project.…

  • Project Management and Best Practice Processes, In Any Industry

    One of the most significant lessons learned going into 2010 is that best (and good) practices are for any industry implementing information technology and system/product development projects. During my career and for the past several years, I have had the opportunity to manage projects in a variety of industries and for a variety of technologies…

  • IT Certifications. Do Certifications Have Value?

    A question I receive consistently when making a presentation on IT certifications. Do certifications have value? How can being Certified Benefit Me? There are certifications in most technologies and disciplines, collectively hundreds. Provided here is a list of several types of Certifications: PMP – Project Management Professional MCSE – Microsoft Certified Systems Engineer CNE -…

  • There are NO MORE EXCUSES for project FAILURE!!

    Eddie R. Williams, PMP Book Title: Software/Firmware Configuration Management (Within the System Development Process) Subtitle: Management Control & Quality Being an IT professional for over 20 years and now a published author and coach, I became very concerned about the high failure rate of projects within the IT industry. I had worked on government, aerospace,…

  • How to Keep Your Sanity and Health Through These Difficult Times.

    Now, getting back to these difficult and hard times. I know many are trying to move forward by maintaining current employment or dealing with being laid-off, getting that next job or changing careers. Through it all, you must include activities to maintain your mental and physical health. Some are listed below. Have a daily routine…

  • Health Check – The 2010 Impact

    “A Restatement” Going into 2010 we still have many concerns that are impacting our lives (individuals and families), our communities, businesses and the IT industry: mergers, the fluctuating stock market, national and international security, continued business financial difficulties and unmet profit margins, layoffs, and regulations’ (i.e., CFR 21, part 11and HIPAA) requirements issued for the…

  • Software Development Best (and Good) Practices: What “best practice” processes do you think are required for IT development projects?

    Best Practice Processes (BPPs) must continue to be estabished and improved for the software development process.  and for the successful projects and programs. The best practice processes are identified below. Several organizations with standards that support these processes are listed. Best Practice Processes: 1. Program/Project Management (and Business Management) (Integration) Use of Experience and Knowledge (Integration)…

  • There are a Variety of Specifications Presented Throughout the Industry to Capture Requirements.

    The requirements document (specification), the result of analysis, sets the stage for the entire and/or any process/phase/activity (design, implementation, etc.) within the development process or life cycle. It is a configuration identification document as well as the design specification/document. The requirements document contains functional/capability, design, interface, data, and other product (software/application/system) requirements. Although it is…