The third and fourth days of the triple conference Better Software East / DevOps East / Agile Dev East held in Orlando, Florida, continued the trend established by the first two, with talks covering a wide range of topics but with a clear emphasis on testing. While days 1 and 2 were filled with half and full-day tutorials, days 3 and 4 were based on one-hour talks.
Between the 14th and 18th November, the three conferences Better Software East, DevOps East and Agile Dev East are taking place simultaneously in the same venue in Orlando, Florida. The conferences are organised around two days of tutorials, two days of talks, and a closing Agile Summit day with keynotes by several international speakers. InfoQ attended the conference to report on its contents.
We have to break the cycle of hiring ourselves over and over again to achieve higher levels of diversity in the software industry, argues Birgitta Böckeler. According to her, things are slowly changing; organizations increasingly focus on diversity and inclusion. There are a lot of people out there who could be great and very happy to become a software developer, but they never even discover it.
As usual, the ThoughtWorks Technology Radar covers four areas - Language & Frameworks, Platforms, Techniques, Tools – each item having one of four recommendations – Adopt, Trial, Assess, Hold. This article lists only what is new and noteworthy in the respective areas.
The impostor syndrome refers to people who fear being exposed as a "fraud". They think that they do not belong where they are, don't deserve the success they have achieved, and are not as smart as other people think. According to Agile Coach Gitte Klitgaard, many high-achieving people suffer from the impostor syndrome. It hinders people in their work and stops them from following their dreams.
Mark Hrynczak, Cloud QA Manager for Atlassian, gave a talk on this year’s company summit in which he shared his vision of how a high valuable QA team should perform. High value for a QA team is defined as being, in the first place, totally aligned with the company strategic goals ,thus contributing to solve the most important problems that an organization might face at a specific moment.
At the recent Agile 2016 conference, InfoQ spoke to Kyle McMeekin about the real world challenges around software testing in agile development, the push to have more test automation and how exploratory testing is different from and more effective than scripted manual testing.
GitLab has released the outcomes of a survey they conducted among software professionals from 362 startups from July 6 through July 27. Main highlights are developers' preference for using latest tools and more collaboration; security is high-priority, but 81 percent admitted to releasing software before it’s ready.
Microsoft has announced Teams, a group collaboration workspace based on chats and integrated with Office 365. Developers have the opportunity to extend Teams with Tabs, Bots and Connectors.
Esther Derby identifies six rules to use when change needs to happen, so that the people involved are honored, and the complexity of the change is acknowledged. Creating an environment based on empathy, knowledge of the past, and a willingness to experiment, makes change less stressful.
People are hardwired to instantly decide who we trust, but also to work collaboratively in small groups. Cognitive biases can get in the way of collaboration, but when you understand how these biases work and what agile practices can do to help, you are more likely to build better interpersonal relationships and create successful products.
In a presentation for OnAgile 2016, Johanna Rothman states that thinking small, and building upon the informal communication networks already at play in an organization, can help scale practices to manage large programs. Rothman provides advice on planning, architectural design, and measuring progress.
Once a startup becomes successful it needs to scale its teams and technology to grow. Scaling has to be done in way that the startup remains effective, and thus capable of quickly delivering products to satisfy the needs of the fast growing user base. Some of the challenges faced are hiring people and onboarding them, along with technology decisions that allow you to grow and get the right people.
Giving teams autonomy to spend 10% of their time for learning reduces delivery time, increases quality, and increases motivation. The 10% rule gives teams full autonomy to work on things they consider important. It results in freeing up people's creativity and letting teams grow their potential.
Lack of autonomy at work is directly related to reduced levels of motivation and engagement, and increased levels of stress and poor health. What can leaders do to improve the sense of autonomy in individuals, thereby increasing levels of motivation and job satisfaction?