Contributions for January Issue of The Best Practice Magazine:
Submit your article about *Configuration Management (CM) for next month's Issue of The Best Practice Magazine. Congratulations to Vicky Webster and Martin Webster (Eds.) who had most views for their December 2018 article entitled 3 Steps to Effective Project Planning and Control. Send your Articles / Presentations / Tools to This email address is being protected from spambots. You need JavaScript enabled to view it.
The CMMI® is an integrated set of best practices that improve performance and key capabilities for any organization that wants to develop better products, components, and services.
The purpose of using any framework is to improve the performance of an organization. For a group that develops products, this can include: improving schedule and budget accuracy, managing risks, eliciting requirements, defining designs, implementation, finding defects early, reducing rework and sharing best practices across the organization.
CMMI practices can be implemented within any life cycle or methodology (such as Scrum, Waterfall, Spiral, Incremental or a hybrid).
One of the Process Areas (PA's) in the CMMI* is Process and Product Quality Assurance (PPQA). This process area supports the delivery of high-quality products and services by providing the project staff and managers with appropriate visibility into, and feedback on, processes and associated work products throughout the life of the project. In this article we share an example process definition for PPQA from one of our clients.
https://www.scrum.org One of the arguments used against Scrum and a common misconception at the same time is the idea that quality is traded for speed in Scrum. As a PST with years of experience in QualityAssurance I decided to challenge this myth. I believe and I have seen many times that proper way of implementing Scrum leads to higher quality products delivered faster than using so called traditional methods. I will look into reasons for coming up with ideas of low quality in Scrum. Then I will explore the idea of quality. Finally I will explain how Scrum supports high quality products.
If you're thinking about ITSM implementation but you're unsure which framework you need, here, we'll try to help you by comparing ITIL and COBIT within an enterprise on a real-life example. But before making any practical comparisons, let’s briefly turn to the ‘theoretical’ difference between COBIT and ITIL.
Quality assurance methods address quality issues in the output of businesses. Lean and six sigma principles apply approaches and metrics to a process to promote efficiency with a minimum number of defects. Companies originally developed all three for application in production. But their success in improving results has led many organizations to apply them more generally to all aspects of the business. Combining them lets companies deliver high quality output with low defects in an efficient way.
An interesting and futuristic piece on Artificial Intelligence (AI) has stated, "Because these AI systems don't actually comprehend the underlying logic of what they do, teaching them to do anything else, even if it's pretty similar — like, say, recognizing specific emotions — means training them all over again from scratch. Once an algorithm is trained, it's done, we can't update it anymore." Scientists and researchers are working relentlessly to improvise the performance of AI and take it to the next level to facilitate various businesses.
