development

The cloud and the rapid migration to mobile devices and the Internet of Things have made traditional software licensing schemes obsolete. Omkar describes new software monetization based on business, pricing models, and usage.

In this interview, principal consultant and Agile Artisans founder, Jared Richardson, explains how misunderstanding requirements can cause major issues within an organization. He covers why team members need to communicate, how big projects are often mishandled, and the value of agile.

Program planners in IT organizations have a dilemma: On one hand, their agile teams tell them that if requirements are defined up front, agile teams cannot operate; but on the other hand, the program’s budget and scope need to be defined so that resources can be allocated and contracts can be written for the work. How does one reconcile these conflicting demands?

Unless I've misunderstood the principle, agile sprints are about layering on features until you arrive at some final release.  

But software can become unwieldy complex and choosing the right data structures and class patterns, for the application, is crucial - isn't it?  

So, how can you decide on the right data structures and classes and patterns, at the very beginning of the process, if in the first sprint, you are only dealing with a few of the overall application features?

Do you continually refactor and re-write as new feature-information is presented? Or is there some overall application design architecture happening up-front?

BTW, I'm not a formally-trained computer scientist, or software developer.