Decades before web apps or smartphones existed, the concept of the separation of logic, presentation, and data layers in software made a lot of sense. That vision evolved into what we now call model-driven development, where rules, workflows, and dependencies are built once, as models in a centralized repository. It's the same basic idea, and it's just as useful, if not more so.
In this interview, Andy Hunt, a consultant, author, and publisher, explains why agile development is in a rut. He also covers why agile is so often abandoned, the issues with doing agile "by the books," and his GROWS Method.
In this interview, Michael Harris, the president and CEO of David Consulting Group, explains his five-step Value Visualization Framework. He discusses how he came up with the idea, how it can help your team right now, and its similarities to the agile methodology.
In this interview, software developer Laurent Bossavit talks about why we need to think more critically about software development. He dispels common misconceptions about the industry and suggests better ways to improve the development process, such as agile and lean methods.
In this interview, LeanDog cofounder Jeff Morgan talks about both the current state of agile and how we can shape its future. He digs into the different ways that people are watering it down, as well as the possibility for some other methodology to break out in the near future.
Even with pages of documentation, there still can be miscommunication and misguided assumptions about a product. A prototype serves as the vision for the product and helps everyone, from a salesperson to an engineer, understand what they are trying to achieve. This article looks at some of the benefits of prototyping early in the development process.
Is the best way to interact with your team in person, with your teammates right next to you? Not necessarily. By working online with remote programmers and testers, people tend to approach problems from some unique perspectives. Read on to learn how imagining an ocean between you and your teammates can actually improve your communication and process.
Thomas Wessel presents how T-shaped and pi-shaped teams based on each member's span of knowledge, ability to collaborate, and depth of expertise play an important part in how effectively your team performs.
We've all been burned working with software code that, if not designed for long-term maintainability, results in expensive support over a product's lifetime. Kaushal explores three approaches that provide guidelines to ensure that software is designed with maintainability in mind. If you're a software developer, read this!