In general, when we talk about the Agile method, it implies an iterative and incremental method of management. It focuses on helping teams in an evolving landscape and maintaining a focus on the rapid delivery of business value. The methodologies used in Agile project management (Scrum, XP, Kanban, and others) all follow the Agile Manifesto that is based on continuous improvement, flexibility, input of the team, and the delivery of results with high quality.
In software development, we often talk about the “traditional model” which refers to the Waterfall Model. Very different to Agile method specially because it’s not iterative, Waterfall is more about a process where you can see the progress “flowing” through the difference phases. In fact it’s a sequential model usually going from requirement analysis, design, implementation, testing and maintenance. The image below illustrates the difference regarding the value proposition of both methodologies and how agile development tends to deliver visibility, adaptability and value in the beginning of the process and reduces a lot the risks during the project.
Agile methodologies address perfectly customer’s needs. During the whole cycle, user involvement is encouraged, providing visibility & transparency, showing the actual progress of projects. As mentioned earlier, Agile method is all about iterative planning, making it very easy to adapt when some requirements change (if you work in the software development industry, I am sure you know how much they can change!). The fact that there is continuous planning and feedback through the process means that we start delivering business value from the beginning of the project. Again, the idea is to deliver business value early in the process, making it easier to lower risks associated with development.
In Agile development, testing is integrated during the cycle, which means that there are regular checkups to see that the product is working during the development. This enables the product owner to make changes if needed and the team is aware if there are any issues.
The product owner is always involved, the progress of development has high visibility and flexibility to change is highly important. This implies engagement and customer satisfaction.
The fact that agile development is iterative means that the features are delivered incrementally, therefore benefits are realised early while the product is in development process.
CEO
Since founding Gunner Technology, Cody has served the company in every aspect of business development and product development.
Executive Assistant
Lisa keeps Gunner on point, ensuring that all tasks are completed on time and with high quality.
CTO
From a contractor to a partner, Dary has been with Gunner since year 1 and embodies the meritocratic spirit and philosophy of Gunner Technology.
Creative Director
As the oldest member of the Gunner Technology team, Keith goes by the affectionate nickname "Papa Keith" and is always available to help out a "young buck."
VP / Engineering
Mahdi joined Gunner at age 18 and quickly rose through the ranks to become VP of Engineering
Developer II
From Sensors and Big Data to Media Queries and Form Validation, Elena has worked on pretty much anything you can imagine.
Quality Assurance Analyst
In 4+ years at Gunner Technology, Ryleigh has created a life-saving testing and deployment process.
Developer III
Skyla is Gunner's go-to engineer when it comes to evaluating new tech. She loves evaluating bleeding edge software and teaching her colleagues what she learns.
Developer II
Kayden holds the Gunner Technology record for most straight hours worked at just under 70. He refuses to quit until the job is done and it's done right.
VP / Product Development
Jeramiah is a wizard at turning loose requirements into a firm vision with a solid plan.
COO
For Kylie, nothing is better than a good process. If it's not documented and repeatable, it's not for her.
Designer II
As one of the most veteran members of the Gunner family, Cory has spearheaded our design efforts on countless projects
Developer I
Yusuf has the memory of an elephant. He is the team's built-in Google and Stack Overflow.
Project Manager
In her own words, Caitlin is a Jill of All Trades - eager to learn and always ready to help.
DevOps Engineer II
Ethan has a mind for infrastructure and a knack for visualizing platform solutions
Designer II
Melissa is known for her odd hours, which earned her the name "Night Walker," but despite the nocturnal tendencies, she's one of the most outgoing members of the Gunner team.
DevOps Engineer I
Nicolas' goal is to learn everything. A voracious reader, the only time his nose isn't in a tech book is when he's scripting a new infrastructure.
A Bug Sprint is a sprint specifically for fixing bugs.
This is a single sprint for answering critical business questions through design, prototyping and testing ideas.
Velocity is a measure of the amount of work a Team can tackle during a single Sprint and is the key metric in Scrum.
A effort point is an abstract measure of effort required to implement a user story.