Agile Manifesto Principles
At J.P. Howard & Associates we produce Smartsheet design and architecture solutions, then we use this knowledge and Agile Manifesto's Principles to provide enterprise-level help desk development, launch, operations and support services freeing up your team to focus on business core tasks.
Agile Manifesto's Twelve Principles
We believe help desks can and should be ran using the best frameworks out there. The Agile Manifesto's Twelve Principles are the guiding principles for the methodologies that are included under the title “The Agile Movement.” They describe a culture in which change is welcome, and the customer is the focus of the work. They also demonstrate the movement’s intent as described by Alistair Cockburn, one of the signatories to the Agile Manifesto, which is to bring development into alignment with business needs.
The Agile Manifesto is at the core of the Agile Movement. Application for Agile outside of software development has even been found, with its emphasis on lean manufacturing and collaboration and communication, and quick development of smaller sets of features under the guidance of an overall plan. The key to its success is that, it is always Agile and able to adapt to change.
1
Customer satisfaction through early and continuous software delivery
Customers are happier when they receive working software at regular intervals, rather than waiting extended periods of time between releases.
2
Accommodate changing requirements throughout the development process
The ability to avoid delays when a requirement or feature request changes.
3
Frequent delivery of working software
Scrum accommodates this principle since the team operates in software sprints or iterations that ensure regular delivery of working software.
4
Collaboration between the business stakeholders and developers throughout the project
Better decisions are made when the business and technical team are aligned.
5
Support, trust, and motivate the people involved
Motivated teams are more likely to deliver their best work than unhappy teams.
6
Enable face-to-face interactions
Communication is more successful when development teams are co-located.
7
Working software is the primary measure of progress
Delivering functional software to the customer is the ultimate factor that measures progress.
8
Agile processes to support a consistent development pace
eams establish a repeatable and maintainable speed at which they can deliver working software, and they repeat it with each release.
9
Attention to technical detail and design enhances agility
The right skills and good design ensures the team can maintain the pace, constantly improve the product, and sustain change.
10
Simplicity
Communication is more successful when development teams are co-located.
11
Self-organizing teams encourage great architectures, requirements, and designs
Skilled and motivated team members who have decision-making power, take ownership, communicate regularly with other team members, and share ideas that deliver quality products.
12
Regular reflections on how to become more effective
Self-improvement, process improvement, advancing skills, and techniques help team members work more efficiently.