From the category archives:

Quality Assurance

Quality Assurance Best (and Good) Practices

by E.R. Williams

1. Prepare and develop a quality management and assurance plan (incorporated) for QA- (which includes verification & validation, test methods/testing, and quality control) in compliance with standards and tailored to the project or program 2. Conduct an assessment, as required 3. Select and use QA automated test tools – Rational, Mercury, Silk, etc. 4. Review [...]

Federal Regulations for Pharmaceutical and Healthcare

by E.R. Williams

It seems to be correct that configuration management could have saved money during Y2K. Within the Healthcare and Pharmaceutical industries, compliance with HIPAA and Part 11, respectively, is still becoming a challenge. You state that configuration management could be helpful with compliance. Why? Yes, Configuration Management could have been helpful then and now. If the [...]

A restatement about lessons learned…

by E.R. Williams

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 [...]

Read the full article →

Lessons Learned

by E.R. Williams

Sometimes we don’t want to admit we have made a mistake or that there were issues with a process or its activities. But how else are we to correct our mistakes and learn from our mistakes; to improve. Whether one thinks it can lead to finger pointing is not a reason not to have the [...]

Read the full article →

Project Management and Best Practice Processes, In Any Industry

by E.R. Williams

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 [...]

Read the full article →

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. 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. [...]

Read the full article →

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

by E.R. Williams

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 [...]

Read the full article →

Health Check – The 2010 Impact

by E.R. Williams

“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 [...]

Read the full article →

Management and Ethics

by E.R. Williams

Management and ethics for business and projects has to be a number one priority for many companies going into 2010 and the 21st Century, but first several issues have to be addressed. Over the past several months, I have had discussions about, and received emails, related to individuals being assigned as project and software configuration [...]

Read the full article →

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

by E.R. Williams

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 [...]

Read the full article →

← Previous Entries