What is Agile?
Agile is an advanced management approach. It may relate to any aspect of management, starting from teams through projects to programmes and portfolios. Agile may deal with small team management but also may help delivering a project in traditional corporate governance.
Experiences collected from multiple projects show that the traditional (waterfall) approach to project management, in many cases unfortunately does not bring the expected results. The reasons may be as follows:
As a result, projects do not end on time, the customerd do not receive what they expect, and the products are of poor quality. This entails a reduction in the return on investment (benefits) or delays its delivery. That's why organizations are looking for other, more flexible approaches to project delivery. However, for organizations that already have standards of formal project management, popular nowadays Agile approaches are dubious and their application appears to be risky.
Such organizations need mature agile method, the method that is nimble and at the same time the method that has a built-in project management - Agile Project Management - AgilePM®
This is a comprehensive compendium of knowledge pertaining to the application of the Agile approach in projects. It includes guidelines on appropriate project management – AgilePM (the role of Project Manager) and information on the professional and Agile culture-adapted business analysis that is very important for the project (the role of the Business Analyst).
Where is Agile?
In order to understand what Agile is and what it is not, we need to try to define the term 'Agile'. There is no single universal definition, and thus there’s a lot of chaos in this field. In broad terms Agile means the presence in every environment (not only design environment) of appropriate “agile” actions, concepts and techniques.
According to such a definition Agile will always mean:
Where can the Agile approach be used? It turns out that on all organizational levels – in the area of business change and in 'business as usual'.
The Agile approach can be applied “everywhere”, that is:
AgilePM and AgileBA
The art of project management and the art of business analysis are the foundations for project’s success, including the one managed in agile style.
We will not exaggerate if we say that there are two entities responsible for the success within the Agile project culture:
The role of the Project Manager is to build this machinery for success. Create processes, empower the team, make sure that its members work well with each other, that issues and risks are resolved quickly, etc.
The Business Analyst makes sure that requirements are properly defined, conflicts omitted, and nothing left out. His/her task is to make sure that the requirements add value to the Business Case, and that the project fully reflects not the selective, fragmentary approach, but the holistic one. This requires a comprehensive approach to the business of the organization on the strategic level, which is also influenced by the respective project. The comprehensive approach to business requires the Agile BA to have competencies in various fields, such as:
Project Manager and Business Analyst help the following principles to function within the project:
Two important principles concerning project cooperation and quality of communication are “Collaborate” and “Communicate”.
Collaborate – this principle concerns and forms requirements mainly for the Project Manager. It is his/her task to ensure that the team consisting of business and technical representatives play “the same game”.
Communicate – problems with communication appear when people talk to one another, but do not understand each other (as in the Tower of Babel, where people were willing to cooperate, but lost their ability to communicate due to divine intervention). They are unable to articulate their requirements or do not know what they need, as this forms tacit knowledge. This has to be elicited with use of Facilitation Workshops, Models, Prototypes and also by observing how people actually work. The role of Business Analyst is to facilitate the communication by application of these practices.
AgilePM and AgileBA training and certification
OMEC offers a wide range of training and certifications in AgilePM & AgileBA, both on Foundation and Practitioner levels.
Check our training paths and available courses.
Benefits for participants
Benefits for organizations
Benefits for participating in OMEC course
AgilePM vs. PRINCE2
Agile PM perfectly links the corporate management processes with agile management and product delivery. Project roles and responsibilities of AgilePM® have their counterparts in PRINCE2®. There are 13 roles defined at the project level and solution development team level in AgilePM, several of these correspond to roles of PRINCE2:
AgilePM management products are not obligatory, however they fully cover project needs when applied in full. There are (among others): Terms Of Reference (Project Brief in P2), Business Case (Business Case), Delivery Plan and Deployment Plan (Project Plan in P2), Risk Log (Risk Register in P2), Issue Log (Issue Register in P2), etc.
T. (+48) 801 55 66 32
F: (+48) 22 207 25 14
ul. Zeusa 41
ul. Św. Filipa 23/1
ul. Św. Józefa 1-3