Agile Model

Agile Model

Agile is a coding practice that follows the rules and principles of agile software development. In this Agile Tutorial, you will learn the fundamentals of Agile, Agile models and methodologies, Agile Vs. Scrum differences, Scrum master training to Agile testing interview questions & answers. This Agile development tutorial is an absolute beginners guide to Agile, and Scrum testing, Basic understanding of manual or automation software testing will be beneficial.

How does Agile work?

• You make a list
• You size things up
• You set some priorities
• You start executing
• You update the plan as you go

How is Agile different?

• Analysis, design, coding, and testing are continuous activities
• Development is iterative
• Planning is adaptive
• Roles blur
• Scope can vary
• Requirements can change
• Working software is the primary measure of success

User stories and estimation

• User stories are features our customers might one day like to see in their software.
• They are written on index cards to encourage face-to-face communication.
• Typically no more than a couple days work, they form the basis of our Agile plans.
• We get them by sitting down with our customers and asking lots of questions.

Iterations

Iterations are the basic building block of Agile development. Each iteration is a standard, fixed-length timebox, where Agile Teams deliver incremental value in the form of working, tested software and systems. The recommended duration of the timebox is two weeks. However, one to four weeks is acceptable, depending on the business context. Iterations provide a regular, predictable cadence for teams to produce an increment of value, as well as to refine those previously developed. These short time periods help the team, Product Owners, Product Managers, and other stakeholders regularly test and evaluate the technical and business hypotheses in a working system. Each iteration anchors an integration point, a ‘pull event’ that assembles various system aspects—functionality, quality, alignment, and fitness for use—across all the teams’ contributions.

Since the shortest sustainable lead time is a significant goal of Lean-Agile development, Agile teams execute a full plan-do-check-adjust (PDCA) cycle as quickly as possible. The PDCA learning cycle (shown in Figure 1) represents the following iteration events:

• Plan –Iteration Planning is the plan step
• Do – Iteration Execution is the do step
• Check – Iteration Review is the check step
• Adjust – Iteration Retrospective is the adjust step

Planning and Refactoring

• Master Story - Our to-do list on an agile project
• Team Velocity - The speed at which we turn user stories into working software
• Planning - iterations = total effort / estimated team velocity
• Refactoring - As we add more functionality to the system we need a way of maintaining our design and keeping our house in order.

Useful Links:
Agile methodology article/eng
Agile methodology article/rus
Agile methodology video tutorial/eng
Agile methodology video tutorial/rus