Welcome to our Think IT Strategic Partnerships Group, two-part series for the fall! The topic of choice after much consideration is; Agile 101. Thank you to everyone that was able to attend our first session last Friday, and thank you to Wayne Arnold and Luann Arnold for leading the discussion. As always, a huge thank you to Medica for hosting our group.
Traditional Project Management is very linear where the phases of the process occur in a sequence. Each project follows the same lifestyle. What’s coming to the surface in today’s industry, is that each project may not fall into the same lifestyle. The rise of an Agile methodology continues to take our world by storm.
In the early 2000s, the Agile Manifesto was born, and it has been continuously picking up steam since. This manifesto lays out four key values as followed:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change
Along with values, there are twelve key principals that stand behind them:
- Satisfy the customer
- Welcome changing requirements
- Deliver working software frequently
- Businesspeople and developers must work together on a regular basis
- Build projects around motivated individuals – and trust them to get the job done
- Face-to-face communication is best
- Working software is the primary measure of progress
- Agile processes promote sustainable development. The sponsors, developers, and the user should be able to maintain a constant pace
- Continuous attention to technical excellence and good design enhances agility
- Simplicity is essential
- Self-organizing teams
- The team reflects on how to become more effective and adjusts accordingly
After discussing the basic values and principles of Agile, we jumped into Scrum. What is Scrum? It is an agile process that allows us to focus on delivering the business value in the shortest time. It is based on three pillars; transparency, inspection, and adaptation. Scrum roles consist of a team, a Product Owner, a Scrum Master, and a Development team.
We went through the different artifacts of Scrum which include a product backlog and a sprint backlog. A product backlog is the master list of work that needs to get done and is usually maintained by the product owner. A sprint backlog is the list of items, selected by the development team for implementation on the current sprint cycle.
This scratched the surface of what Agile is, and how it started. During our next session, we will jump into how we can effectively utilize it in our space.
What would you like to see discussed at our part-two meeting titled Applied Agile and Strategic Partnerships?