In the final series post, we are going to discuss the Process pillar.
The Modern Application Process Pillar focuses on how software development teams are engaging with their business partners and customers to build applications.
Traditional applications are built by disparate product, application development and testing teams. Interaction between the teams is done through liaisons and lengthy requirements documents.
Modern applications are built by teams that contain a cross-section of skills and responsibilities. Team members will include product owners, user experience, development, testing and release (configuration) management. Ideally, the team will share the same space in an office, but often that is not possible. If it is not possible to share the same physical space then the modern application team must use tools to collaborate and coordinate their work throughout the software development lifecycle.
Participation in social networks has grown rapidly over the past decade. Consumers regularly interact with friends and colleagues on these networks. They follow people and are followed by others. They tweet, retweet, share, link, like and comment on content that gets shared with people of all walks of life.
Consumers crave social interaction and want to provide feedback into how their applications are built to better support their needs. All technical teams (development, testing and operations) want to be involved early in the development cycle to ensure that applications are built well. Providing feedback throughout the build process provides a sense of ownership among end-users and improves later adoption.
There is growing evidence that informed groups are better decision makers than a few individuals. In “The Wisdom of Crowds,” James Surowiecki argues that large groups of people are smarter than an elite few, no matter how brilliant those few are. This approach leverages the collective intelligence and experiences of many employees to build better applications.
Successful IT Organizations create cross-functional teams that allow team members to express their opinion and allow the team to set the right application development priorities to support the organizational goals.
Join us next week for the conclusion to this series.