Start your agile development team with the mantra: No manual test cases! Quality comes from collaboration and rapid feedback, not documentation. Let’s take a look.
Lean practices have revolutionized the manufacturing industry; the application of lean principles have also had a big impact in construction, IT, services and health care. In this webinar we will share some of those principles and practices and give examples how they can be used in a large variety of projects.
Has your organization or quality management team gone through the effort of adopting the Plan, Do, Check, Act (PDCA) strategy for making improvements to various processes? This talk will dive into what it really takes for an organization, or even a department within, to make true gains from the PDCA process.
Save Time With Tools + Templates
The Pareto Chart is a simple yet powerful tool that allows one to distinguish between the critical few and trivial many. While this is a quality tool, it can be used by any project team for any project type. Microsoft Excel currently does not have built-in functionality to create a Pareto Chart; this Excel template has an in-built macro that can generate a Pareto chart with just a click of a button.
While numerous key performance indicators (KPIs) typically influence IT projects generally, the benefit of tracking all of them may be outweighed by the cost to do so. Therefore, each project must carefully select and manage those KPIs most relevant to its specific situation. This sample template can be used to define KPIs; also included is a table with examples of possible KPIs for each of the previously defined project-critical success factors (PCSFs) and a metric (measure and dimension) for each KPI. Use in conjunction with the article Determining IT Project Health.
Use this assessment to determine if a system is ready to go to production. It is a series of spreadsheets that allow different modules to have both ticket tracking (bugs) and other criteria; then based on thresholds, the system can be assessed as ready or not ready to go live.
This single-page PDF flowchart shows the workflow diagram that clearly illustrates the stages of a typical project, which consists of relations between all parts of the project cycle. Workflow diagrams are used to represent the transferring of deliverables during the project phases, to study and analyze the working processes, and to optimize a workflow. Use it as a visual refresher or teaching tool.
El código es la firma de un desarrollador en un proyecto de software, y no todos los desarrolladores cumplen las reglas de los buenos estándares de codificación. Asegúrese de que su equipo de desarrollo deje un legado de codificación que no solo implemente la aplicación en cuestión, sino que pueda ser entendido por otros y mantenido durante futuros ciclos de desarrollo.
Learn From Others
Every project manager is familiar with the project management triangle, comprised of scope, time and cost. Quality, resources and risk are additional factors that must be accounted for to achieve project success. The focus here is to understand how these constraints are still relevant in the age of agile.
Management philosophy believes that what is measured gets managed. Hence, metrics suggest whether the process is in order or needs external interference. They form the basis of control in any organization. Learn more about the key features of effective metrics.
Quality has always been the key factor in successful project management. The philosophies of lean, agile and kaizen are proving to be key enablers of delivering quality products and services consistently.
A quality audit determines a level of conformance to requirements of a system, process or product. The requirements can be company policies, standards and procedures, or norms and regulations. This article contains general information about quality audits, as well as rules to follow for both auditors and auditees.
IT application development projects can be challenging and stressful. The efforts of the successful team need to be recognized and celebrated. In this article, the author makes the case for greater celebration of application code and the coders who write it.
Commitment to quality and implementation of programs aimed at process improvement are becoming focal points to increase overall performance. The incorporation of total quality management (TQM), a leading management philosophy, with strategic planning is natural and inevitable.
Though there is lot of bias toward increasing velocity every iteration to release more features faster, if there is no attention to quality, the system will soon become fragile—and will not be able to house scope changes in the future. How do we balance these forces?
One common failure pattern in creating agile development teams is taking a regular software tester, assigning them to the new team and expecting them to perform in new ways that elevate the team to high performance. What does a good agile tester look like? What should we expect of them? And how do we find them?
Most project teams test their own projects when it comes to component, system and regression testing instead of having a third set of independent eyes do it. But is this the best idea?
Don’t forget the most important consideration in quality management: human beings. In this article, the writer addresses a way of handling quality management with this most important aspect at the forefront.
Ask a Question