Agile

Working software is the primary measure of progress. – Agile Principle #7 Agile Principle 7 offers a simple guideline: true customer value means delivering working products*. This principle is important because it: Quickly demonstrates quality. Working product means...

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. – Agile Principle #6 The sixth Agile Principle addresses communications management on an agile project team, stating what many successful...

Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. – Agile Principle #5 The fifth Agile Principle focuses on the project team and emphasizes the importance of trust, support and motivation....

Business people and developers must work together daily throughout the project. – Agile Principle #4 As we continue our review of the principles behind the Agile Manifesto, we come to principles 4-6. These principles focus on the project team and how individual team...

Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter time scale. – Agile Principle #3 The third Agile Principle rounds out the customer-focused principle group and emphasizes the fact that delivering...

Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. – Agile principle #2 This principle stresses the importance of embracing change on your projects. On agile projects, you welcome change at...

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. – Agile Principle #1 This agile principle refers specifically to customer satisfaction.  By delivering product features and functionality that offer value to...

Learn how effective sprint planning drives productivity and keeps Agile teams focused on priorities.

Master Agile release planning techniques to align your team’s efforts with product goals and business objectives.

One of the most popular ways of estimating requirements is by playing estimation poker, sometimes called Planning Poker®. Estimation poker is a game scrum teams can use to determine relative requirement size and to build consensus among development team members. When...

Find out how Agile sprint reviews help track progress and align product development with stakeholder expectations.