lia is your ideal precursor to more complex frameworks such as SCRUM, but it also works very well on its own. Because it has such a small footprint, it fits virtually any existing organisation structure and works with all roles and responsibility already in place. This is the first time it has been documented after 2 years of use; excuse the stock images. Start using lia today and watch your projects and team improve by following these 4 steps:
Many Agile implementations fail not because the framework isn't suitable. Frameworks are just tools. Without knowing why we use these tools, they become worthless. That is why understanding lia means to first understand Agile. lia promotes the Agile Manifesto as a basis for this understanding.
Anything that goes on in your project gets put into the backlog. The lia backlog is absolutely prioritised: The most important stuff goes to the top, the least important is at the bottom. If you start from the top, this allows you to be incredibly efficient about when you write specifications. Every requirement uses the user story format and the INVEST formula to determine what needs doing - and why.
Once you have collected and sorted your requirements, it's time to actually get to work on them. The Sprint in lia is a one-week timebox with a fixed amount of work your team commits to finishing during that time. All the work should come from the top of the backlog and run through 3 states: Todo, Doing and Done.
The lia meeting takes place at the intersection between two sprints and asks three simple questions: What did you accomplish this sprint? What are your going to accomplish next sprint? And what is keeping you from doing your best? These questions will help you to better understand what your clients want, deliver the most important features first and to constantly improve the way you work.
To start using lia, all you need to do is read up on the 4 steps, fill your backlog and call everyone in to your very first lia meeting. That's it. Everything else about lia will unfold through your work on the backlog and your continuous improvement. There is no reason to rush, but if you want to get a head start, read up on these best practices.