Digital forms help reduce paper waste and costs of printing and storage. FieldElite app can help your business get started creating digital forms for your Field Service Workers.
Is Your Project Agile, a Scrum or a Kanban?
Few projects pan out the way we expect when starting out. This is normal in any creative planning phase. We half suspect the ones that follow a straight line are the exceptions to the rule. Urban legend has it; Edison made a thousand prototypes before his first bulb lit up, and then went on to comment, “genius is 1% inspiration, 99% perspiration”. Later, he added that many of life’s failures are people who did not realize just how close they were to success when they gave up.
So be it to this day, and so be it with project planning too. There is no one size fits all approach when it comes to it. Agile, Scrum and Kanban each have their supporters and places where they do well. Project planning often works best when we use a sequential combination of them, appropriate to what is currently happening on the ground.
Of the three, Agile is by far the most comprehensive. It provides a structure that begins with project vision / conceptualisation, and goes as far as celebration when the job is over, and retrospective discussion afterwards. However, the emphasis on daily planning meetings may dent freethinking, and even smother it.
Scrum on the other hand says ‘forget all that bureaucracy’. There is a job to do and today is the day we are going to do it. Although the core Agile teamwork is still there it ignores macro project planning, and could not be bothered with staying in touch with customers. If using Scrum, it is best to give those jobs to someone else.
The joker in the pack is Kanban, It believes that rules are there to substitute for thought, and that true progress only comes from responsible freedom. It belongs in mature organizations that have passed through Scrum and Agile phases and have embarked on a voyage towards perfection.
That said, there can be no substitute for human leadership, especially when defined as the social influence that binds the efforts of others towards a single task.
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 Roadmap 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.
IT Systems Implementation
Although a rigorous Acceptance testing process can spot a wide spectrum of flaws in a newly constructed IT system, there is no way it can identify all possible defects. The moment the IT system is delivered into the hands of actual end users and other stakeholders, it is effectively stepping out of a controlled and secure environment.