Blog

Part 11 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
The tenth Agile principle focuses on keeping the solution as simple as possible while maximizing value and quality. Agile processes focus on finding the simplest way possible of solving a business problem with quality, not finding the fastest way to code the solution.  Sprints are kept as simple as possible to ensure that all work gets prioritized by using the backlog as the gatekeeper.  In the Read Entire Entry

This is the third installment in a multi-part series to address the basics of performance testing applications. It’s for the beginner, but it is also for the experienced engineer to share with project team members when educating them on the basics as well. Project Managers, Server Team members, Business Analysts, and other roles can utilize this information as a guide to understanding performance testing process, the typical considerations, and how to get started when you have never embarked on such a journey.
Planning an effective Read Entire Entry

Part 10 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
Principle nine is all about good design and technical excellence.  One of the biggest challenges facing teams that are attempting to do Agile development is the natural urge to just jump in and start coding based on a lose set of requirements, without any real design.  This is natural, but almost always results in negative impacts to the project timelines, because the team has to go back and do Read Entire Entry

This is the second installment in a multi-part series to address the basics of performance testing applications. It’s for the beginner, but it is also for the experienced engineer to share with project team members when educating them on the basics as well. Project Managers, Server Team members, Business Analysts, and other roles can utilize this information as a guide to understanding performance testing process, the typical considerations, and how to get started when you have never embarked on such a journey.

Performance Testin Read Entire Entry

Part 9 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
Agile principle 8 deals with managing a fresh team.  This is one of the most telling characteristics of Agile and Fragile teams.  Agile teams see projects as a marathon made up of individual sprints.  For the team to make a sprint at the expense of the overall marathon is not acceptable.  Agile teams ensure that the amount of work that the team takes on is realistic and paces the effort of the team Read Entire Entry

This is the first in a multi-part series to address the basics of performance testing applications. It’s for the beginner, but it is also for the experienced engineer to share with project team members when educating them on the basics as well. Project Managers, Server Team members, Business Analysts, and other roles can utilize this information as a guide to understanding performance testing process, the typical considerations, and how to get started when you have never embarked on such a journey. This blog series will cover Read Entire Entry

Part 8 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
The seventh Agile principle is all about quality.  It says that WORKING software is the primary measure of progress.  I spoke with a noted Agile coach and keynote speaker at a conference recently.  We were having a discussion about the fact that the words quality and testing don’t show up anywhere in the agile manifesto or in the 12 principles.  The point of his argument on why it wasn’t there Read Entire Entry

Part 7 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
Agile principle 5 is all about the people you chose to be a part of your team.  If focuses on the principle that if you get the “right” people, give them the right environment to be successful, and then get out of their way, they will deliver great things.  In an Agile world, the best and brightest are sought out to be a part of the team, and then they are enabled to make the right decisions as a Read Entire Entry

Part 6 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
The fourth Agile principle focuses on ensuring that collaboration between the business and the teams that deliver is active.  The principle goes so far as to say that this collaboration needs to be a daily activity, not just a weekly update, or at the beginning and end of a sprint. When the business is engaged in the project, it has a much higher chance of success. Remember, the Voke survey states Read Entire Entry

Part 5 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
Principle three of the Agile principles is all about speed to value. What this principle tries to accomplish is to find the fastest way possible to get value into the hands of the customer.  This assumes several things.  First, you are adding value and not limiting value.  Second, it assumes that the faster I can get value into the hands of the business the faster they can bring in revenue. And Read Entire Entry