We are uncovering better ways of developing software by doing it and helping others do it.
-Manifesto for Agile Software Development, 2001
Fundamental to the modern software delivery life cycle is an iterative approach to demonstrate progress and business value.
My delivery experience in Agile methodologies, principally Scrum, Extreme Programming (XP), and Kanban.
One of the twelve principles from the manifesto of Agile Software Development is to deliver working software frequently, in weeks rather than months.
- Manage teams in the benefits and advantages of using Agile methodologies, roles, ceremonies, and artifacts.
- Manage and coach product managers, and development teams in the adoption of key facets of Scrum.
- Fluent in the use of ceremonies such as planning poker, user story estimating, backlog refinement, sprint prioritization, sprint retrospectives, and release planning.
- Proponent of continuous incremental improvement from teams and individuals.
In order to provide best in class tools to allow Agile teams to operate at their optimum level of productivity, I have set up suites of industry-standard tools, including Trello, Slack, GitHub, Jira, and Confluence.
A key aspect of using these types of tools is not just their set up, but their tuning, adoption of best practices, consideration of the needs of the team, and connectivity so they communicate with each other over common APIs, and provide the best possible experience.
Tools adopted by Agile teams should meet the needs of the team, project or client demands - and actively improve productivity and team throughput.
One challenge of Agile adoption has led to the training of users with zero-to-little previous experience in key facets, how to use provided tools, and the sharing of best practices to accelerate Agile adoption.