That’s a statement we hear every now and then- be agile. But what the hell does ‘be agile’ mean anyway? Well if that’s what you have been looking for you have come to the right place.
Before we dwell into the dark dungeons of ‘being agile’, let’s first take a look into what agile is. Agile software development refers to a set of software development methods based on iterative growth where requirements and solutions are developed through association between self-organizing cross- functional teams.
Now for the next part, consider this breakdown of agile in project management that is ‘being agile.
With agile project management there aren’t really any deadlines which are usually given by project managers otherwise in any organization or firm, and can become a real pain for software developers. Developing a software aka product/service completely bug free is an extensive, time taking and nerve wrecking process – that needs constant modification and improvements. But with agile it’s different, one doesn’t have to worry about meeting deadlines because agile breaks down tasks and sets goal for every day.
Estimations can be a quite sore concept for any developer. Developing big software systems is in its core a very complex task. However, it is a bit less stressful not to have to approximate the time for a task if you spend more time on it than your original estimate, because you are solemnly involved in making the product better and better. This is a motivator for the developers, as it peaks their interest in making a worthwhile product rather than merely completing a task for a job because you are getting paid.
Planning & Reviewing
Since there are no estimates it means there are basically no charts, estimated velocity on which the team should be working and no sprint either. So an ultimate target is set and the team always have their eyes on the bigger picture – it’s not like nothing is reviewed- quarterly and mid quarterly meetings are held which can assure one that they are headed in the right direction. Mid quarter sessions basically review the status of the target and the progress that has been made in the meanwhile while in the quarterly sessions the targets are set for the team.
As an end note it’s easy to confuse agile with scrum but do not forget scrum is just a subset of agile.