Agile
Agile is a method of working in a group that groups categories into what should be a priority compared to what shouldn’t.
Agile groups focus more on being flexible within the team and changing plans based on what works for the individual members.
Agile generally prefers shorter time frames and works around motivated individuals to get work done fast and efficiently.
It depends on flexibility in the fast paced system, quickly working out what works and what doesn’t and adjusting accordingly.
It doesn’t rely on creating a detailed plan and sticking to it because of the limiting effect that has.
Encourages diversity of ideas and lots of communication within teams to ensure the best way of working.
Agile produces work faster than traditional waterfall project management, meaning the focus is more on quantity than quality but the team can receive feedback from a client on quickly produced and easily changeable products, rather than changing the entire plan if a client doesn’t like it.
Agile focuses more on consistent evaluation and optimization within each step compared to waterfall project management
Waterfall project management

Agile project management

Scrum
Scrum is a tool used in agile project management to produce work. Sprints are used to separate the project into sections to complete. Sprints involve a short planning stage, followed by implementation, within which is a ‘daily scrum’ or ‘daily stand-up meeting’ to alter the product based on the clients and team members preferences, When the implementation is complete, there is a review of the produced work. Anything that is not satisfactory is included in the next sprint and the first sprint is complete.
As shown below, the planning phase consists of the product backlog and the sprint backlog, first detailing the most important aspects of the product that need to be created, anything the team is unsure about can be added in future sprints when the product is more fully developed. The sprint backlog is presumably created in order of most to least important features and completed according to that.

Reflection
It’s important to regularly update the plan or outline for the project so if anything has proven to be ineffective, unimportant, or more important than expected, the project management documentation has to be updated to work around peoples ideas and changing opinions. If the plan isn’t changed, people may continue working on something that is no longer necessary and neglect a new priority that came up during implementation.
The group can tell if they are on track for a deadline by setting smaller deadlines within the larger project. It allows for more flexibility. Deadlines can be set for each individual feature and if they are not complete, it’s a sign they are falling behind. If the team falls behind, they can make a note of everything they still need to do and adjust the plan/sprints to fit within the remaining time until the deadline.











































