Skip to main content

Resources

Comments

Post a Comment

Popular posts from this blog

PDCA & SCRUM (or Agile); Why is it important?

The PDCA (Plan DO Check Act) cycle was made popular by Dr. W. Edwards Deming. This is a scientific cyclic process which can be used to improve the process (or product). This is cyclic in nature and usually time boxed. Plan  This is the first stage of the process. During this step the team discusses the objectives, the process and the clear conditions of exit (conditions of acceptance). This stage sets the measurable and achievable goals for the team. DO Team works together to achieve the objective set in the planning phase. Team works with the set of agreed process. Check Once the implantation is done team regroups and verifies the output and compares it to the agreed conditions of acceptance decided during the planning phase. The deviation, if any, is noted down. ACT If any deviation in planned tasks is observed during the Check stage, a root cause analysis is conducted. Team brainstorms and identifies the changes required to prevent such deviatio...
Post a Comment
Read more

Why is potentially shippable product quality important

Agile teams work in iterations. During this period, they are supposed to work on product increments which can be “delivered” at the end of iteration. But how you know that the correct product was delivered? Many teams have different kinds of acceptance criteria and Definition of Done (DoD). But in many cases, this “done” is not the real “done” there might be some testing pending, some integration or review pending or anything else which prevents the actual use of the product increment. Many of these teams will need additional iterations to finish hardening their products. Many teams will implement different types of “gates” or approval steps to move to next stage. The free flow of product will be interrupted. They might end up doing mini waterfall within their agile process. Many don’t even realize this. This results in poor quality and requires additional effort to “harden” the product. Potentially Shippable Product increment The acceptance criteria and DoD should be modified...
Post a Comment
Read more

Key principles for robust and maintainable software development

 When it comes to robust and maintainable software development, several key principles can greatly contribute to the quality and longevity of the software. Here are some important principles to keep in mind: 1. Modularity: Divide your software into smaller, self-contained modules or components that perform specific tasks. This approach allows for easier development, testing, and maintenance. Each module should have well-defined responsibilities and interact with others through well-defined interfaces. 2. Separation of Concerns: Ensure that different aspects of your software, such as user interface, business logic, and data storage, are handled by separate components. This separation helps to improve clarity, maintainability, and reusability. 3. DRY (Don't Repeat Yourself): Avoid duplicating code or logic in multiple places. Instead, create reusable functions, classes, or modules that can be shared across the codebase. This reduces maintenance effort and helps enforce consistency. 4...
Post a Comment
Read more