Skip to main content

Posts

Showing posts with the label Agile

Agile Scrum Definitions

  Overview Over the past few years working within the Agile Scrum teams I have seen at some places there are not clear with the basic simple terms of Agile scrum definitions and I thought of writing this blog post based around exampling the simple basic terms definitions we use in Agile Scrum terms. Product Owner The primary decision-maker on the scrum team. Scrum Master Leads the meetings and standups, removes roadblocks and oversees the scrum team. User Story A brief explanation of the who, what and why behind a project. Tasks An item that needs to be completed by a scrum team member. Backlog A repository of the project ideas that may be executed in the future. Blockers Anything that is preventing a team member from completing their work. Minim Viable Product (MVP) A base-level project intended to show proof of concepts. Kanban A visual framework for tracking steps in a process that uses columns and status indicators moving from left (beginning ) t...

12 Principles of Agile

      Overview Agile is a collection of values and principles hence Agile’s the real utility is giving people a common foundation for making decisions about the best way to develop software effectively and to deliver on time. The 12 Principles   of Agile Below are the 12 Principles of Agile, which I feel are very important to follow/apply to any given software production. As delivering cost-effective, bug-free and on-time software is one of the main objectives for any software production cycle.  Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.  Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.  Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.  Business people and developers must work together daily throughout the project.  ...