Agile Sprinting in the Age of Low-code | LANSA Blog
Low-Code Mobile App Development and Data Integration - LANSA Skip to content

App Development & Modernization Tools for Complex Projects

Low-Code Platform

LANSA's low-code development platform accelerates and simplifies the creation of enterprise apps while making your development team more productive. LANSA puts you back in control.

Learn more
Mobile Development

LANSA makes it easier than ever to take your apps mobile. Build mobile-first apps as easily as web apps using a single platform.

Learn more
Enterprise Integration

LANSA offers powerful integration choices for your web and mobile apps. We support a range of options to make integration fast and easy.

Learn more
IBM i Modernization

LANSA is the only low-code development platform to natively support IBM i. You can build new apps and modernize existing ones - with native web and mobile support

Learn more

Trusted by thousands of organizations worldwide

The Low-Code Platform That Benefits Every Technical Role

Visual LANSA impacts every area of the business, delivering company-wide innovation, productivity and control.
For IT Managers

LANSA lets your team create apps up to 10x faster than usual, reducing the time- to- market for new apps and helping clear your application backlog.

Learn more
For CxOs

LANSA equips your IT team to innovate and deliver new apps in the time frame the business needs. Your team becomes more productive and responsive.

Learn more
For Developers

LANSA’s low-code platform allows you to become a full-stack developer delivering web and mobile apps faster and easier than ever before.

Learn more
For ISVs/SIs

LANSA’s low-code platform helps build easy-to-maintain apps for your customers, reduces time-to-market, and makes your team more productive.

Learn more
Noun Quote

“With LANSA we can help our customers be more agile and responsive to new business requirements. That's extremely important in the transportation industry. Enhancements and customization are now simple and fast, meaning that we can respond quicker to customer requests.”

“With LANSA we can help our customers be more agile and responsive to new business requirements. That's extremely important in the transportation industry. Enhancements and customization are now simple and fast, meaning that we can respond quicker to customer requests.”

“With LANSA we can help our customers be more agile and responsive to new business requirements. That's extremely important in the transportation industry. Enhancements and customization are now simple and fast, meaning that we can respond quicker to customer requests.”

Glenn Gundermann, Application Development Manager, Nulogx

“Our ERP system happens to run on IBM i, which is often and mistakenly earmarked as a legacy platform. Using LANSA and with a renewed focus on our existing ERP system, we have proven to be more flexible and productive than a packaged ERP like SAP ever could be.”

“Our ERP system happens to run on IBM i, which is often and mistakenly earmarked as a legacy platform. Using LANSA and with a renewed focus on our existing ERP system, we have proven to be more flexible and productive than a packaged ERP like SAP ever could be.”

“Our ERP system happens to run on IBM i, which is often and mistakenly earmarked as a legacy platform. Using LANSA and with a renewed focus on our existing ERP system, we have proven to be more flexible and productive than a packaged ERP like SAP ever could be.”

Arnold Hendriks, Application Development Manager, Bidfood

“The LANSA portal is a crucial part of our digital strategy and plays an important role in remaining competitive. It offers a new way to add value to our services, above and beyond just selling a product.”

Michael Hall, Head of Digital, Elders Rural

previous arrow
next arrow
Slider
X

FREE WHITEPAPER

The Power of Coding in a Low-Code Solution

Free Virtual Event, October 2020

A full day of Low-Code sessions for Devs, CxOs & everyone in between

FREE eLearning Site

Enroll in free courses for every stage of the Low-Code journey

Agile Sprinting in the Age of Low-code

Agile development provides many benefits to software development, if executed well.  I’m not going into a lengthy definition of the intricacies and pitfalls of how you run an Agile development project.  This article takes a deeper look at one aspect of Agile: The Sprint.

Perhaps slightly over-simplified for the most puritanical Agile process enthusiasts out there, this short description for The Sprint provides a good starting point to build a discussion: A sprint is a short race to a defined end.  It’s simple.  It’s straightforward.  It’s short.

The most often used sprint duration is two weeks. So, in two weeks you want to achieve a set goal, or goals, with a defined result or deliverable.  Business and IT work together and fine-tune what is being achieved during the Sprint.  It’s like rapid prototyping, but you don’t want to throw it away afterwards.

Now let’s consider the emerging low-code development platform movement.  One of the first things to make clear is that it is not “no-code” – but “low-code”.  I make this distinction quite clear, because at some point, if the defined end-goal of a Sprint includes a real business application with at least a few complex business rules and multiple data sources, some coding will be required somewhere.

Don’t slow down your Sprint to a Stroll

The goals of low-code mesh well with the Sprint concept. Low-code provides a developer with the capability to rapidly build complete applications that can span multiple user experiences (for example web and mobile).  A good low-code platform handles all the underlying tedious and mundane aspects of software development, like creating the data layer, handling communications between the front and back ends, addressing cross-browser inconsistencies, negotiating integration between disparate data sources, etc.

There are plenty of examples in the real world where we apply technology to make the task quicker.  We use cars instead of a horse and buggy.  We use chainsaws instead of axes.  Engine powered ships replaced sails and so on…

Yet many Sprinting development teams are still holding on to development tools that require loads of effort and programming tediousness. And thus, their resulting Sprints do not actually result in potentially shippable software as their methodology suggests.

Their pretty and spatially planned multi-coloured 3M sticky-notes won’t compensate for the self-limiting assumptions they have accepted to conjure the notion of a Sprint. It’s simply a chunk of work being performed in two weeks with the accepted defined result of that with which the next two-week Sprint will commence work with in one fortnight.

Some may argue that the use of frameworks addresses much of the mundane coding.  However, this author has seen numerous frameworks come and go over relatively short periods. This is adding to the cost of development – not reducing it.  It means that an organisation is producing “legacy applications” at an alarming rate – because these applications need to be maintained; and having three, four or five different frameworks is creating a productivity drag – like barnacles on a ship – and deepening technical debt.

Get more out of your Sprint with low-code

To become truly agile, it is crucial to move to a low-code application development approach. Consider these important elements when selecting a low-code development platform to transform your Sprints from fortnight chunks-of-work to end-result-bearing races:

  1. Visual creation of UI components – allow the developer to easily develop UI views and have the software handle underlying areas such as swapping between views in a Single Page Application model.
  2. Assist the developer in styling with built-in support for Google’s Material Design. Including complementary colour schemes.
  3. Provide a “Mobile First” approach to UI development, including responsive design handling. But don’t forget about your power users! When building desktop applications, make sure you can strike a different balance between UI screen real estate and productive control.
  4. Create a Data Services layer for accessing underlying tables and insulating your UI and business rules from the details of database access.
  5. Support for collaborative development.
  6. Support for one-click deployment, whether that be to on-premises servers or cloud environments.
  7. Make it easy for developers to re-use components.
  8. Provide a business rules engine to centralize tasks like data validation, and the synchronization of data management across multiple user experience deployments, etc.
  9. Make it easy to do active prototyping – where this work is retained in the actual development.
  10. And after it’s in Production – make it easy and quick to maintain.

The Agile Sprint has provided a great approach for building modern complex business applications.  Developers need to update the tools they are using to get more out of Sprints. Throw away the axe and grab your chainsaw!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.