Kanban is often used to manage work, but the concepts of kanban can also be used to guide a journey of change in an organization. This is a case study of an insurance company that used kanban to get change done to improve visibility and predictability and engaging their people.
Testing teams and their managers need to unlearn the traditional mindset and practices when they want to adopt an agile way of working says Navneet Goyal. At the International Conference on Software QA and Testing on Embedded Systems he gave a talk about how test teams should adapt themselves in agile projects.
Organizations should create an environment where people feel empowered and trusted, with a culture where leaders can thrive says Pawel Brodzinski. An interview in which Pawel shares his view on leadership and culture, explains what it is that makes leaders thrive in organizations and what organizations can do to create an environment where leadership would emerge.
Testability must be explicitly designed in the system said Peter Zimmerer from Siemens AG. Test architects should drive testability and collaborate with architects, designers and testers in using good design and engineering practices. At the QA&Test 2014 conference Peter gave a tutorial about design for testability for embedded software systems.
Blockades in work, like insufficient information, unclear requirements or having to wait for tools or systems to become available can have a systematic cause. It could be the case that similar problems that block the team keep happening until the underlying causes are addressed. You can use your blockades as treasures of improvement to sustainably improve the way work is done.
Ryan Mckergow explains various ways to set up story walls for agile team. This post includes setting up columns, rows, selecting colors and avatars for the story wall.
Bob Marshall explains the reason of failing of scrum master in most of the organizations as the lack of awareness on the part of adopting scrum and scrum master’s responsibility to tackle organizational dysfunction.
Software development initiatives include different types of meetings, spread across the whole development process. A post on the Mobile Orchard blog explains tips and tricks to check and improve the effectiveness of these meetings.
Agile software development is sometimes perceived as an undisciplined way of working. There are organizations which use that perception as an excuse to not adopt agile. According to others agile is actually a more disciplined approach than waterfall for software development. Let’s explore how discipline plays a role in agile and why discipline is considered important for agile to be successful.
In the book series the art of managing remote teams authors share their experiences and provide advice on establishing and working with remote teams. The books are intended for people who are about to setup an offshore or nearshore team, or people who are already managing a remote team and want to improve.
Valentin Tudor Mocanu described upgraded form of pair programming using pairing and non-solo development.
In agile projects the product owner is often seen as the person who primary assures the connection between business and IT. But for effective IT-Business alignment having a product owner is not enough. What can people from the business, demand and supply parts of the organization do increase the effectiveness of IT – Business alignment?
The State of Testing 2013 report contains the results of a survey done by Joel Montvelisky from PractiTest together with Tea-Time with Testers. The survey, which has been filled in by people from testing and QA communities, provides insight in the adoption of test techniques and practices, test automation, and the challenges that testers are facing.
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.
Long working days, deadlines and team pressure can impact the quality of the software that agile teams deliver. What can we do to prevent that from happening and enable teams to improve the quality of their software? Some suggestions are to arrange for scope and deadline slack, adopt pull systems, and to make sure that people can slow down and get enough sleep.