How is Agile different from traditional SDLCs? Agile allows for a
more flexible framework on requirements gathering, to avoid rushed changes at later
launch/release phases of the project. This is achieved through bringing
together the Iteration planning and testing, within the later Development phase
of a project. It means that a Project Leader is only primarily focused on the
top-level requirements and estimates at the first phase of a project. The
critical Bottom-level requirements (or mini projects) are gathered and planned
according to priority.
Knowing when to use Agile
What I have found is whilst Waterfall and V-Lifecycle work very well
for the smaller and more standard projects with less attributed risks, Incremental
phase, and Agile style methodology can greatly benefit larger and more
complicated projects. Obviously I am biased to within the Digital industry
where requirements do change more to real time due to fast moving technology
changes. The need to keep up is always apparent.
What has become apparent to me is that there are two key areas,
which businesses can focus to help them embrace Agile; These are:
1) The ability to expect and adapt
to changing requirements. Are there studio or company restraints that are now
allowing for this?
2) Demonstrating often, reducing
risk and providing transparency. Incorporating more opportunities for iteration
planning and testing during development, through the use of Wire Frames and Use
Case modelling.
These key areas have been developed as part of the 12 principles of
Agile Software Manifesto, which helps solidify the holistic view to Agile at
it’s core
Elements of Agile methodology
Additionally, it helps to incorporate correct Scrum and Sprint
methods within the lifecycle, to really benefit the project. Scrums should be
held daily and only last around 15 minutes, as a way to quickly capture and
solve the biggest issues happening within a critical project. Therefore it
should only include the priority team members at that time. My recent training
and resources have told me that for a Scrum to be advantageous as part of an
Agile framework, it must follow the below, otherwise it won’t allow you to
achieve real Lean solutions for your project:
- Should only last around 15 minutes daily
- What has been done since last meeting?
- Do you have any obstacles?
- What will you do before next meeting?
Further reading
BA Times offer free training Webinars for developing BAs if you are
interested to find out more about how Agile can work for you.
No comments:
Post a Comment