Becoming Nimble the Agile Project Management Way

In dictionary terms, ?agile? means ?able to move quickly and easily?. In project management terms, the definition is ?project management characterized by division of tasks into short work phases called ?sprints?, with frequent reassessments and adaptation of plans?. This technique is popular in software development but is also useful when rolling out other projects.

Managing the Seven Agile Development Phases

  • Stage 1: Vision. Define the software product in terms of how it will support the company vision and strategy, and what value it will provide the user. Customer satisfaction is of paramount value including accommodating user requirement changes.
  • Stage 2: Product Roadmap. Appoint a product owner responsible for liaising with the customer, business stakeholders and the development team. Task the owner with writing a high-level product description, creating a loose time frame and estimating effort for each phase.
  • Stage 3: Release Plan. Agile always looks ahead towards the benefits that will flow. Once agreed, the Product Road-map becomes the target deadline for delivery. With Vision, Road Map and Release Plan in place the next stage is to divide the project into manageable chunks, which may be parallel or serial.
  • Stage 4: Sprint Plans. Manage each of these phases as individual ?sprints?, with emphasis on speed and meeting targets. Before the development team starts working, make sure it agrees a common goal, identifies requirements and lists the tasks it will perform.
  • Stage 5: Daily Meetings. Meet with the development team each morning for a 15-minute review. Discuss what happened yesterday, identify and celebrate progress, and find a way to resolve or work around roadblocks. The goal is to get to alpha phase quickly. Nice-to-haves can be part of subsequent upgrades.
  • Stage 6: Sprint Review. When the phase of the project is complete, facilitate a sprint review with the team to confirm this. Invite the customer, business stakeholders and development team to a presentation where you demonstrate the project/ project phase that is implemented.
  • Stage 7: Sprint Retrospective. Call the team together again (the next day if possible) for a project review to discuss lessons learned. Focus on achievements and how to do even better next time. Document and implement process changes.

The Seven Agile Development Phases ? Conclusions and Thoughts

The Agile method is an excellent way of motivating project teams, achieving goals and building result-based communities. It is however, not a static system. The product owner must conduct regular, separate reviews with the customer too.

Check our similar posts

Advanced Business Management

Our consultants are highly trained to provide complex management solutions and strategy planning for your business. You can count on us to improve performance and your business skills, while cutting costs.

We ensure full support in a broad range of business management areas, such as:

Business Strategy

Knowing how and when to make the right strategic move is critical to your success in today?s dynamic environment. Our Strategic Management Consultants provide solutions for a tighter integration of your vision, values, and mission statements with the strategic management process.

The result is a stronger alignment of your operating activities with your goals, and also an improved internal infrastructure to support and manage the strategic management process.

Business Process Improvements

In our years of activity, we have developed a robust process to ensure Business Process Improvements projects are implemented successfully. To achieve a positive outcome a number of factors must exist and we?ll make sure your company manages to get the right mix of: sponsorship management and commitment, process improvement goals, right motivations, cultural issues management, provision of adequate resources and funding, and availability of standards and procedures.

Performance Management

An effective performance management system integrates all aspects of the organisation from a shared vision, through a common language, and establishes a culture of accountability and results. It provides more of a holistic way of managing your organization that is more powerful than its individual parts, and without forsaking the values of the organisation.

Change Management Services

Economic downturns, fast rising new competitors, and even climate change, can force companies to scale down, engage in mergers & acquisitions, or transfer to a new location. We?ll help you through every step of the change process, from: evaluating the required change by conducting diagnostics such as change complexity, causal, structural, and context analysis, managing stakeholders including your sponsors, top executives, managers, and personnel, planning for the change, and managing the change process itself.

Project Management

Whether you need help for a single project or much more, we’ve got you covered. With us you get a coordinated, presence-of-mind approach to project management that will point all of your projects to an overall strategic direction, no matter how complex or simple these might be. Our services incorporate all project-related activities including: programme management, project risk management, project review and audit, project rescue, and project governance.

Interim Management

Our resources have an MBA and/or professional accounting qualifications with an average of 10 ? 30 years of progressive work experience with public companies, in complex private equity environments, and/or privately-held middle market companies. We not only offer the most highly qualified project / interim resources to our clients, but we also allow for an interim-to-hire provision in our contracts.

It has proved mutually beneficial to our consultants and clients to have the option for longer term employment opportunities after having worked together on a project / interim basis.

 

Can you do away with the Project Initiation Meeting?

Project initiation meetings are often skipped to fast-track projects. Once a sponsor is found, organisations go straight to project planning and execution. But based on our own experience, holding a project initiation meeting can actually eliminate many issues that may crop up in the future and hence may speed things up instead in the long run.

It is in the project initiation meeting where your project objectives and scope are clarified and all stakeholders are brought to the same page. Project sponsors and stakeholders will have to know in a nutshell what is needed from them, what the possible risks are, what different resources are required, and so on. So that, when it’s time to proceed to the next phase, everyone is already in-sync.

So what are taken up in such a meeting? Perhaps an actual example can help. Sometime in the past, we set out to work on an eCommerce website project. After conducting the project initiation meeting, these were some of the things we were able to accomplish:

  • Identified deliverables e.g. site design, interface to payment system, etc.
  • Come up with the project phases
  • Agreed what should be in and out of scope
  • Defined the acceptance test criteria
  • Identified possible risks
  • Identified the possible training and documentation work needed
  • Established whether any analysis was required, e.g. as with regards to payment interfaces
  • Formulated disaster recovery plans
  • Defined roles and responsibilities
  • Drafted timelines and due dates

Aren’t these covered in project planning? If the project is a big one, the answer is no. In a large project, project planning is a much more exhaustive activity. In a project initiation meeting, only the basic framework is defined.

Some questions may still remain unanswered after a project initiation meeting, but at least you already know what answers you need to look for. In the example we gave earlier, we left the meeting knowing that we needed:

  • a list of all necessary hardware to estimate the costs
  • to identify possible dependencies we might have with third parties
  • to identify what software had to be bought and what skills we needed to hire

When it was time to proceed to project planning, everyone involved already knew what direction we were taking. In effect, by not skipping the project initiation meeting, we were able to avoid many potential obstacles.

Failure Mode and Effects Analysis

 

Any business in the manufacturing industry would know that anything can happen in the development stages of the product. And while you can certainly learn from each of these failures and improve the process the next time around, doing so would entail a lot of time and money.
A widely-used procedure in operations management utilised to identify and analyse potential reliability problems while still in the early stages of production is the Failure Mode and Effects Analysis (FMEA).

FMEAs help us focus on and understand the impact of possible process or product risks.

The FMEA method for quality is based largely on the traditional practice of achieving product reliability through comprehensive testing and using techniques such as probabilistic reliability modelling. To give us a better understanding of the process, let’s break it down to its two basic components ? the failure mode and the effects analysis.

Failure mode is defined as the means by which something may fail. It essentially answers the question “What could go wrong?” Failure modes are the potential flaws in a process or product that could have an impact on the end user – the customer.

Effects analysis, on the other hand, is the process by which the consequences of these failures are studied.

With the two aspects taken together, the FMEA can help:

  • Discover the possible risks that can come with a product or process;
  • Plan out courses of action to counter these risks, particularly, those with the highest potential impact; and
  • Monitor the action plan results, with emphasis on how risk was reduced.

Find out more about our Quality Assurance services in the following pages:

Ready to work with Denizon?