In the past, software products was planned, developed and tested for years until the product was finally released to customers. During the long planning and implementation phases many things can change from the used technology to the customer needs. Due to the changes or problems that need to be handled in later phases, companies lost a lot of money because of the slow and wrong project management approaches.
However, things have changed since the year 2001, when the agile manifesto was introduced to revolutionize software development. The agile manifesto contains 12 principles with a clear focus on the customer, the software delivery, the collaboration inside a team and the outcome rather than processes and documentation.
Now, 18 years later since the agile manifesto was introduced by a group of software developers more than 70% (according to PMI) of all organizations use agile methodologies such as SCRUM and KANBAN.
In this article I want to focus on the agile methodology of SCRUM and why SCRUM matters for you and your company.
With the launch of modern smartphones in 2007 and one year later with mobile app stores, software products are used by their customers from every possible location. Furthermore, the products must serve the users’ needs wherever they are and whenever they want to use it. With the rise of high quality mobile phones and products the expectation from the software increased. Users are way more emotionally attached to their mobile phones and to the software that runs on it.
But what has this example to do with SCRUM? Read more
Since 6 years the state of testing survey is conducted by PractiTest’s QA Intelligence Blog in collaboration with TeaTime with Testers.
Over the last years the survey provided unique insights into the testing craft around the world and helps us to shape our
work and community.
I highly recommend you take some minutes and to fill the survey to provide yet another awesome report for all of us.
Please follow this link to fill the survey!
Once the survey results are live, I will let you know on my blog.
Agile methodologies such as SCRUM and KANBAN are the most used frameworks within small and independent software development teams. In theory SCRUM and KANBAN are really easy to establish in teams and companies. However, the majority of software development and product companies have more than one development team working on the same product at the same time. Does that mean companies with more than one development team can’t establish agile methodologies?
Of course not, but companies need to have the right environment and the right mindset inside the company to scale agile software development across all disciplines.
Scaling Agile Development The Right Way
The first piece of puzzle every company has to find is the north star. With the help of this product metric, the company can define its vision and mission. This will help the software development teams in terms of guidance, stability and focus.
The next part of the puzzle is the development infrastructure. It must be modern built up on the latest technologies and patterns to build a microservice architecture to provide agile teams the possibility to release whenever they want independent from other teams inside the organization.
Last but not least, it’s important to keep the agile development teams small and as independent as possible. With the help of agile coaches, the right agile mindset can be established inside the team. Once all of this is in place, it’s time to scale across the organization.
Read more about this topic in my lastest blog post I wrote for Applause here:
Maybe you have seen it already on YouTube or twitter. Currently, I am recording an online testing course for Ministry of Testing about mobile testing. In this course I will teach you the fundamentals of mobile testing.
The course will include the following topics:
- History of mobile devices
- Hardware of mobile devices
- Mobile Device Fragmentation
- Mobile Data Networks
- Comparison between iOS and Android
- The different mobile app types
- Mobile app stores
- Mobile app business models
In each lesson I will talk about the testing impact and will provide usefule resource for you to kickstart your mobile testing activities.
Take a look at the course teaser.
The complete course will be online soon in the dojo at https://www.ministryoftesting.com/dojo/courses.
I am looking forward to your feedback and the discussions about mobile testing in the club as well on the ministry of testing community page.
Every product owner, designer or development team has ideas for a potential new mobile product or feature. Some ideas are worth following, some are not. But how does one know, which idea to follow and which one to drop?
The answer is simple, a team has to try it out. A team has to innovate on mobile product ideas to find out if the product idea is something the customers have waited for and want to use. If a team has lots of new ideas and don’t know which one to innovate first with, it’s recommended to bring all the ideas to a meeting or workshop and to check if e.g. the ideas fit either to the target customers, the needs or solving a specific problem. At the end of the meeting or workshop a prioritized list must be the result.
In order to bring the idea to the app store there are multiple stages a product team must go through. The first phase is the fake it first phase. In this phase the team is drawing rough sketches of the potential new mobile product. The drawings can be done on real paper or with the help of wireframing tools.
The drawings will be connected to a first user flow and later on tested with real customers.
But what comes next? Find this out in my lastest blog post for Applause, I wrote more about this process of innovating on product ideas, which tools to use to create a wireframe and what a mobile innovation lab has to do with mobile product development.
Read the complete article here: