Best Practices:
- You know something is wrong if retrospective meetings happen only on the if-time-allows basis.
Agile masterminds recommend to pre-plan a retrospective meeting after every single sprint. It’s not like these meetings should eat into the project’s time anyway. - Remember that the point of Agile is to fine-tune and adjust as the product development unfolds, especially in mobile development.
Apple and Google introduce yearly OS updates that bring access to new functionality. The Stakeholders may request to update argentina phone number data their app to support the most recent features.
5. Toolset Chaos
Frankly, this typically happens with the teams that have just switched to a new Agile flavor: they start looking for new exciting tools. Like stickies on the wall or spreadsheets aren’t that good anymore. In all seriousness, switching to Agile app development doesn’t mean switching gear altogether.
Best Practices:
- To get the project rolling make use of the tools that your team already knows.
Chances are, these solutions offer some sort of Agile project management features. Otherwise, they’d be obsolete by now. - Focus on individuals and interaction rather than processes and tools.
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
Some of the Best Agile Tools:
There are so many popular tools in Agile software development that every app development team is likely to find the one that will work best. Here are some of them that we recommend for Agile mobile app development process:
- Atlassian JIRA
- Miro
- Trello
- Asana
- Monday.com
But there are many more reliable Agile tax on property used for commercial purposes project management platforms. So choose whatever looks familiar and works best for your app development process.
6. Two-Pizza Team Size
Jeff Bezos’ two-pizza team rule 100% applies to an Agile team working on a mobile app. As Jeff promptly put it, a team can be efficient if two pizzas feed everyone. Richard Hackman stresses that more team members lead to more links between people.
“The larger a group, the more process problems members encounter in carrying out their collective work.”
— Psychology of Leadership
The cost of coordinating and communicating contact lists between group members gradually brings team productivity to a screeching halt.
Best Practices:
- Divide the teams of 10 and larger into separate subgroups working on a specific part of your app. For instance, you can split the backend and app development teams.
- Aim for six-eight people tops for a minimum action unit on your app development project.
7.
The most prominent advantage of Agile is you don’t need to maintain extensive documentation. Contrary to this opinion, some teams take it as no documentation is required. The Agile Manifesto states loud and clear:
Simplicity — the art of maximizing the amount of work not done — is essential.
At Velvetech, we document everything to ensure project knowledge retention. Large-scale mobile apps can take more than six months to deliver. You would imagine it’s vital to have at least some documentation for the mobile projects of such scale.
Check out how Scott Ambler, author of several books about Agile app development, compares approaches to documenting in the traditional and Agile software development lifecycles.
Best Practices:
- Always document the app architecture.
- Document everything else that adds value to the product for each sprint.
- There should be a single person responsible for all documentation on the project.
