Agile

Before discussing the core concepts of agile project management, it is important to answer two questions: * What does the term “agile” stand for in the context of this management methodology? * Where did this methodology originate from?

Agile is defined as 'Having the capacity to embrace change.' Sounds a lot like Self-Efficacy. Self-Efficacy is defined as 'the ability to create a desired change.'

It's a process of iterative planning, continuous testing, dynamically changing requirements, iterative managing & development - which results in the ability for collaboration and a better final product.

This is essentially the way I write.

My writing as iterative process. Meaning I don't really know where I am going with a particular piece until I start writing it. The sentence that follows this one is part of a continuous waterfall.

If you were software, what would be written on the back of the box (the programs features, benefits, system requirements, and limitations?)

How can you make changes in requirements part of the development process?

Rather than change orders being a non-negotiable element, can you use them to produce a better product? YES.

Lack of an agile discipline will result in substandard results, dissatisfied clients and readers.

The agile model is fluid and is geared to deliver high quality specific product features over short development cycles of one to four weeks called sprints. I routinely run 10-day bursts which I call sprints.

The agile project management model.

The SCRUM methodology.

The ability to innovate on the go

Accountability and iterations.

In an agile model, there is no specific owner is in charge of the whole development process or singly accountable to success or the failure of the project. Instead, it is co-owned and the success or failures fall on all the stake holders.

Dynamic in nature: project scope, cost, personnel, quality, risk, and requirements.

Activities (punchlist items) are tracked on a daily basis and shared with all team members. It creates a team atmosphere where all members truly feel a sense of belonging to the project, are encouraged to give input and feedback with the intention of improving the end result.

Since the process is iterative in nature, agile results in a product that is continuously evolving. A result is improved communication between the creator (zoom out) and the creative team (zoom in).

Iterative tools are better at accommodating ongoing changing author and reader requests.

The focus on the 10-day sprint creates deadlines that drive action.

The 10 day sprint template is used and the clock provides a constant 'sense of urgency' reminder.