Trust an agile methodology

low code tips

“Capture your requirements to an extent that creates a backlog, so you can get going quickly. Don’t document absolutely everything up front, and have the confidence in an agile methodology, combined with a low-code solution.

“It’s like that first two, maybe four-week cycle of capturing requirements in the low code solution when… you see the light bulb moment and the confidence [increases]. It’s having that confidence within the business community, particularly the business stakeholders, to follow an agile methodology…because you truly can build rich functionality very quickly.”


Focus on the minimum viable product

low code tips

“It’s quite easy to extend scope. I think business professionals are so used to projects taking a long time that if they don’t get all their requirements in phase one, there will never be a phase two, there will never be a phase three. Have confidence that in eight weeks you can build some very, very rich capabilities. Have a minimum viable product, deliver after the first release and then have a second release, a third release, where you have incremental business value, that’s deployed out to the business community.

“Don’t wait for a ‘big bang’, because low-code now – and Appian – can deliver incremental value very quickly, rather than waiting for a 6, 12 or 18-month big bang. Deliver iteratively with incremental releases.”


Embrace collaboration

low code tips

“Building powerful business applications with low code isn’t solely an IT responsibility. It’s about collaborating between the businesses, which clearly know the requirements, IT professionals who use a low-code approach to accelerate building applications. And then the change and transformation C, who are involved in driving change and agility and innovation into the business. So having those three constituents truly working together.

“I’ve seen for a number of years of my career, historically, kind of silos between the business, IT and change. And I think organisations are doing as well as breaking those silos down and having that closer collaboration. Again, low-code facilitates that. With a programming language it is so hard to do that because only a small number of people know what Java really means and how it works and so on. And so you need a low code approach in order to bring that collaboration together.”

Back to top

Share this article