From the category archives:

Quality Assurance

Quality Assurance (QA)

by E.R. Williams

Too often we call quality assurance just “testing” or “quality control”, where both traditionally have been performed under the umbrella of Quality Assurance (QA). QA, a planned process/activity, tailored to the program/project, is about ensuring compliance with standards, regulations, plans, and requirements, prevention, and trend and problem analysis for corrective action. This is the reason [...]

Read the full article →

Do the “Right Thing” for your project, the customer, the company, and yourself…

by E.R. Williams

We are into the 21st century. Do the “Right Thing” for your project, the customer, the company, and yourself. If not, it has consequences as we all have/are seeing. It’s the ethical thing to do, maintain your integrity and the company’s credibility.

Read the full article →

Documenting Lessons Learned

by E.R. Williams

Documenting lessons learned. It’s a day to day attitude and activity. Based on the number of failed IT projects for the past decade it seems that transfer of knowledge and feeding back (sharing) lessons learned, did not take place. Frequently we see lessons learned not identified, discussed, documented and archived on a continuous or daily [...]

Read the full article →

Technology Project Challenges… Continued

by E.R. Williams

Skill Set Requirements – Not Just Being Certified Resource requirements for a project or program have become a day-to-day challenge. RayAnn identified the challenge of resource availability in a previous information source, at the same time you have to ensure that the resource is the “right fit”; has the appropriate skill set. At one time, [...]

Read the full article →

Beyond Project Close Out

by E.R. Williams

Recently, I received several emails and telephone calls to discuss a problem with a web site requiring revising or revamping and applications requiring modification, enhancement or replacement after the projects had closed and warranty periods had expired. The changes or request for changes seems to have been announced without prior notice or discussion with key [...]

Read the full article →

“The process to find another job has taken longer than I anticipated. I have almost terminated or stopped my search efforts.”

by E.R. Williams

We have all been there before but when you go through it, it becomes a very personal thing. One thing I do know, you can’t give up on your search activities. Your positive efforts, no matter when or how long it takes through these times, will prepare you to take that next positive step forward. [...]

Read the full article →

Unclear Development Processes and Methodologies

by E.R. Williams

There are many methodologies for IT development and implementation projects (hundreds, because many companies have their own “flavor” of a methodology or two, and maybe several) but they all should have/contain basic processes/activities: feasibility/initiation; planning; requirements analysis; design (Architecture/Detail Design); implementation/construction/build/test (unit, integration, functional\\(capability/qualification; system test (stress, functional, performance, volume, etc.); user acceptance test; operational [...]

Read the full article →

How do you ensure all deliverables are released and delivered for each process/activity; ensuring accountability for each deliverable when other individuals have responsibility to prepare/author the documentation?

by E.R. Williams

Project Close Out – Project Deliverables and the Close Out Letter A restatement from Project Management Lessons Learned. Conducting project close out: Ensure that (not limited to or in a particular order): A project close out meeting is conducted with the customer/client to define that all close out criteria have been satisfied (financial included) Any [...]

Read the full article →

Change and Configuration Control Beyond Project Close Out

by E.R. Williams

Change is inevitable. Change Management covers all changes within the scope of a program/project. Configuration Control, a process/activity under configuration management, covers changes to the product/system and is applied after a product/system is approved and baselined.(See the book Software or Firmware Configuration Management on the complete process.) Although both change and configuration control are activities [...]

Read the full article →

Software Vendors and Their Tools/Applications

by E.R. Williams

Now after knowing the process, hopefully it allows you to make a better selection of products to automate and make the development process more efficient. It begins with requirements (which can’t be over emphasized). For some time we have had software vendors developing Computer Aided Software/System Engineering (CASE), applications, and tools for processes (i.e., Project [...]

Read the full article →

← Previous Entries

Next Entries →