We’ve all heard of the Agile Software development methodology; but how many of us are actually using these principles while developing LabVIEW code? My guest, John Sextro is an Agile coach and an expert in the field of Agile Software development. Listen to this episode of the VI Shots podcast where I ask John about the Manifesto for Agile Software Development, and we walk through the 12 principles behind the Agile manifesto. This conversation is just the beginning of an exploration of this topic. I’m planning on having John back on in the future to discuss Scrum, which is the leading agile development methodology.
I believe LabVIEW is by-design, a language that can thrive within an Agile development environment. You can quickly get software working and data displayed on a UI within a short time frame. I’d like to hear your feedback on this topic. Do use Agile? If not, then why not? Post you concerns and questions in the comments below and John will visit this post to answer your questions.
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
- Our highest priority is to satisfy the customer through early and continuous deliver of valuable software.
- Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
- Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
- Business people and developers must work together daily throughout the project.
- Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
- The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
- Working software is the primary measure of progress.
- Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
- Continuous attention to technical excellence and good design enhances agility.
- Simplicity–the art of maximizing the amount of work not done–is essential.
- The best architectures, requirements, and designs emerge from self-organizing teams.
- At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.