AGILE Development
AGILE Development
A way to work where you strive to get feedback very quickly, from a working product that have a limited number of working functions.
Letting the feedback lead you in your development.
When developing Software this method is often used (with software there are possibilities to achieve a working software having limited functions and then gradually work towards a fully functional Software)
AGILE is a bottoms up method where the coworkers make the decisions
Product Owner (PO)
- Working with Agile you most of the time have a Product Owner (PO)
- The PO has the responsibility to maintain and revise the Product backlog.
- The product backlog can be seen as a wish list/an order to the Sprint team.
The function with the highest profitability is highest on the list indicating
what development will start with that function. In the following sprints (se
below ) we go further down the list integrating less profitable functions in
the design. Hence we get a focus on the most profitable functions early on.
- The PO needs to be a people’s person, someone being good at handling
many types of persons everything from the developer, customers to the
finance persons.
- Their responsibility is somewhere between Finance and Solution
management.
- POs interest is when and what something is done - not How
- The PO is total responsibility for the product, its development, its life cycle
and its value creating.
- To be able to take this responsibility the PO needs to have mandate to take
all the decisions regarding the product
- Has the money to invest in the product development of new functions,
production facilities, equipment or something else needed for the product
- Meaning that the developer comes to the Product Owner and asks for
money when needed
- This means that money is not spent and tied up for the hole project but for
different specific tasks when needed
AGILE Development
Working with agile you divide the working group into smaller teams working in so called sprints, short tasks that can be finished in a couple of weeks time producing a tangible result which is working and can be tested (fail or success).
It is important to define the area of responsibility for the group and interfaces between the group and the neighboring groups.
Sprint Teams
- Adapt all the time, be flexible be openminded let the best ideas win.
- Empower your coworkers.
- Let everyone plan their own targets, judge performed activities and plan
next steps. Meaning that they control their own work.
- Customer Collaboration – the earlier you can involve the customer the
earlier you can get feedback on whether you are on the right track or not.
Team meetings often lead by a so-called Sprint master
Often standup meetings or short sitting meetings covering:
- What worked well this week
- What didn’t work well
- What we agreed on working with next week (look at the product backlog
and the sprint backlog)
- Are there any obstacles or do you need help with something
- Are there items in need of going on the sprint backlog list?
Product Owner (PO)
- Decides when a solution can be used in production.
- Meaning the solution can be used now, or do we need it to be a part of
more sprints, or just wait.
AGILE Development project
Benefits of working AGILE:
- Rapid feedback (gives you an early feeling if you are moving in the
right direction or not)
- Quick adaptation to changes
- Empovered coworkers
- Increased information flow both up and down the hierarchy
- Increased control
- Gradualy increase the functions that are worked with gives a
concentration in the whole group (dont start with all functions at
once)