Behavior driven development (BDD) can be used to improve communication between testers, developers and the business. For example you can use given-when-then scenarios to develop test scripts and at the same time define the requirements of the system. BDD involves all team members and helps them to think about the product.
There is an evolution going on in testing. It used to be that testing was about confirming to the specification. Testers were often brought in too late and had too little influence, but that is changing now as Cirilio Wortel explained in his talk on the evolution of software testing.
There is a common understanding among agile organizations that they should aim to build the products that are “good enough”. Scott Sehlhorst, explains the different perspectives of “good enough” in his blog.
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.
Behaviour-Driven Development (BDD) can help in overcoming the gap between the developer’s understanding of what needs to be built and the business’ understanding of the technical challenges caused by the requirements. The reason is improvement in communication between the two groups, Alistair Stead and Konstantin Kudryashov explains in their Beginner’s guide to BDD.
Niels Pflaeging, founder of the BetaCodex Network, did the opening talk organize for complexity - how to get life back into work on the second day of the Dare Festival Antwerp 2014. He explained how decentralizing organizations is paramount to increase their performance and agility.
At the recent Project Management Institute Global Congress the Business Analysis Practice Guide was announced, to complement the Professional in Business Analysis certification which was launched in November. InfoQ spoke to Dave Bieg, Business Analysis and Requirements Program Manager about the certification and the practice guide.
The real requirements of a product are not the functions that are needed, or user stories that have to be delivered. It is the possible improvement of performance that customers can get from using the product said Matteo Vaccari. At the XP Days Benelux 2014 conference he facilitated a workshop together with Antonio Carpentieri about defining the value that is needed by customers.
To thoroughly remove waste in a process you need flow to deliver just in time, and mindfulness and situational awareness in organizations to handle problems with processes and built in human intelligence. Organizations apply concepts from flow to develop what is needed and when it is needed and use pull to prevent inventories. What they also need is “Jidoka”: mindfulness and situational awareness.
Agile testing can be used when developing software for automotive systems. To adopt agile techniques in automotive the automotive SPICE V-model needs to be adopted to agile. One result from combining agile and SPICE as Xavier Martin presented at the QA&Test 2014 conference is that “intensive automated testing and client demonstrations helps to produce better products, rising clients satisfaction”.
Continuous deployment helps organizations in delivering high quality software fast through build, test and deployment automation. It gives earlier return on investment, earlier feedback and easy process of deployment. Is continuous deployment also good from business perspective?
Teams can become so focused that they forget the world around them and risk losing contact with stakeholders. This makes it difficult for them to know what their customers need and how end users will use their products. At the ASAS2014 conference Daisy Rasing-de Joode will show how successful agile teams create synergy by being interdependent and highly collaborative with their environment.
To incrementally develop and deliver products using agile software development, requirements are gathered and organized into a product backlog. A requirement technique that is used in agile software development is use cases. Some techniques to apply use cases for managing product requirements in agile are use case 2.0, slicing and laminating.
The Manifesto for Agile Software Development values "working software over comprehensive documentation". This core value asks us to think about how much and which kinds of documents are needed and when they need to be written.
Would better user stories improve software delivery? Gojko Adzic thinks applying small changes to the way teams manage their user stories can have a huge impact on the actual outcomes of their software delivery. He announced that he wants to write a book about improving user stories if at least 5000 people show that they are interested by pre-registering themselves in January.