At the Agile 2016 Conference InfoQ spoke to Wesley Coelho, Senior Director of Business Development for Tasktop, about the communication challenges inherent in DevOps and how to overcome them; how DevOps and agile expose organisational silos and waterfall communications flows that need to become adaptive and automated.
Architecture principles epitomize architecture's function: to clearly define the necessary constraints on a system's design without prescriptively defining all the design details. A good set of principles can provide context and justification for design decisions and can foster team collaboration and communication.
Ultimate Software settled on Kanban as its scaled methodology which went hand-in-hand with the company’s culture of autonomy. Teams define their own process and apply policies specific to their own context. Through the innovative use of flow practices and principles, Ultimate has been able to achieve many of the benefits of a Lean-Agile implementation without the use of a heavyweight framework.
At the recent Agile 2016 conference, InfoQ spoke to Dennis Ehle about the evolution of DevOps and the importance of having visibility into how value is delivered over the DevOps pipeline.
“Designing the Requirements: Building Applications that the User Wants and Needs" proposes an alternative way to deliver spot on solutions.
Standardizing Requirements Descriptions on Scrum Projects for Better Development and Testing Quality
Standardizing requirements descriptions on Scrum projects benefit development and testing quality by enablling full coverage, minimizing errors, and facilitating scheduling and requirements changes.
The book Liftoff, Second Edition provides practices and insights for chartering teams by understanding needs, building trust, and defining how to interact in the team and align with the organization.
Our efforts to improve software development face the question what to focus on. We can’t be predictable if we are not adaptable. What we really need is to be predictably adaptable.
Bimodal IT has been supported by many and criticized by many. InfoQ reached out to enterprise experts to dig deeper into the pros and cons of this strategy and how/when/if is it applicable.
Iterative development requires gradual flow of small-sized, prioritized requirements from end customers to delivery teams. The use of all-conclusive, rigid, non-negotiable BRDs leads to dysfunction
Iterative development requires gradual flow of small-sized, prioritized requirements from end customers to delivery teams. The use of all-conclusive, rigid, non-negotiable BRDs leads to dysfunction.
The story of how Medtronic Neuromodulation realized that in order to modernize their processes while maintaining compliance, adopting integrated Application Lifecycle Management was necessary