A service is a logical construct owning a business capability and made up of internal autonomous components or microservices that together fulfil the responsibilities of the service, Jeppe Cramon suggests continuing a previous series of blog posts clarifying his view on building services around business capabilities and bounded contexts.
InfoQ did an interview with Gil Zilberfeld about managing the expectations that organizations have of agile and how to prevent misconceptions, valuable ideas and practices from agile and what the future will bring for agile.
Technique of "value points" to determine the value delivered by any software project.
Popular configuration mechanisms like conf.d pose multiple problems when trying to converge system configuration using configuration management tools. Ish-Shalom proposes five design principles for configuration that prevent those problems. The core ideas being the use of a configuration API and the separation of configurations based on the type of system updates they require.
The product owner value game is a card game for teams. The objective of the game is to deliver as much value as possible. Teams learn to prioritize backlogs, plan iterations, and deliver results. The game helps teams to talk about agile principles, and exchange experiences.
Tester should go beyond their testing discipline and go into the organization. By asking questions they can start a movement that increases product quality and helps organizations to become more successful as Mike Sutton explained in his closing keynote at the Agile Testing Day Netherlands 2015 about test beyond quality – beyond software.
The Yelp engineering team have stated that moving to a service-oriented architecture has allowed them to scale their development process and maintain a rapid pace of software delivery as the team and codebase has grown. This has been achieved by focusing on distributed systems education, creating a set of basic service design principles and implementing a supporting infrastructure.
Dave Gray talked about how a connected company focuses on customer efficiency instead of company efficiency at the No Pants Festival 2015. A connected company has multidisciplinary teams where people work together to deliver a product or service. People working at a connected company feel empowered, they are able to solve problems together and to better serve the needs of their customers.
Business process management software provider Effektif today announced the open sourcing of their workflow engine. The new model allows developers to include Effektif workflows from within their applications via Java and REST APIs
Introducing and managing change in organizations can be challenging. InfoQ interviewed Jason Little who is involved in organizing the Spark the Change Canada 2015 conference about the leadership and management approaches that radical companies use, on finding better ways to manage people and about what will happen to management in the near future.
Organization that are adopting agile often look for ways to establish self-organized teams where team members are able to take more responsibility. Agile software development teams could improve their decision making by using the consent principle and sociocratic procedures. Sociocratic governance structures can also be used to scale up agile principles to every level of the organization.
The assumption that a large system must have a single environment, often with a one-to-one mapping between a project’s scope and the system built are challenged today Stefan Tilkov explains when looking into ways to split a large system into smaller parts and comparing the characteristics of systems, applications and microservices.
Agile suggest teams to self-organize their work. The questions arise what self-organization is and what organization can do to make it possible for teams to become self-organizing.
The World Wide Web Consortium (W3C) has published the Pointer Events standard as a recommendation for wide adoption, but its future is in doubt as Apple and Google are refusing to implement it.
Mark Little discusses the anatomy of microservices, how they can be used, and why you may want to temper your enthusiasm to get them to production.