Best practices for successful M-Agile
The Agile Manifesto was published in 2001 and now nearly every software development team claims to be following Agile practices (to some extent). Client server and web app project teams have reached a level of maturity enabling frequent releases with a predictable velocity and high quality. Agile practices move organizations towards embedding quality throughout the process.
But, these same teams are feeling daily pressure to deliver similar capabilities on mobile devices. Business is shifting to the digital experience and mobility is the central focus. Organizations succeeding to deliver standard web and other technologies are now struggling to achieve the same maturity in the mobile (web & native) world or what we are calling M-Agile (Mobile Agile).
In this session we will explore why the unique aspects of mobile app development are changing SDLC (software development lifecycle) practices. There is no magic to adapt current practices. Rather, we will share a recommended set of practices to achieve predictable velocity and deliver high quality mobile apps. The conversation will specifically address how to implement continuous integration (CI) to achieve the fast feedback / fast correction cycle required to drive mobile app engagement. CI can help teams also achieve Continuous Quality by embedding functional and non-functional verification in every build.
Outline/structure of the Session
Some topics that will be covered on the session:
- Mobile trends
- Why M-Agile is different? Challenges & implication on agile mobile development process
- Best practices to be successful in M-Agile focused on how to build successful continuous quality process
- How to leverage the apps store
Attendees will get set of practical best practices & tips
Mobile & Web developers, Mobile & Web Dev managers, Build managers, Mobile \ Web project managers, QA, QA manager