Project Management for mobile websites is a special kind of approach based on its various requirements and limitations. In my experience I handled Mobile websites for Social Media, Business Functional Applications, Online Product Purchase, News and Media presentations, Entertainment Content downloads, and Travel and location based services. For every single project, we faced a small change in our process, basically learned from experiences. We followed agile approach for almost all our projects in simple way to make the project management painless.
I am planning to write more about project management for this platform, but as a start, let me share some key points.
- Organize a basic requirements analysis meeting with all stakeholders and document the requirements in easy functional stories
- Build a product Backlog from the requirement analysis and consider it as first level defined scope
- Present the overall project goals – the overall solution model , as a guide for priority setting
- Build a team & assign key roles – the team should include stakeholders, quality assurance and implementation team members. Key roles and responsibilities should be assigned for scrum master, product owner, designers, developers, quality assurance and stakeholders. Document it for future benefits
- Define and publish a communication plan for the community of stakeholders
- Define backlog stories derived from basic analysis and user stories
- Prioritize backlog and communicate sprint release goals with stakeholders
- Plan your sprint – a scrum master is responsible for ensuring tasks are completed
- Define sprint length – we plan for 10 days
- The product owner should present stories to lead the team through the project proposal document, and define acceptance test criteria
- Scrum master and QA should sit with the developer to confirm scope, expectations, and technical implementation details – including the QA level and documentation details.
- Estimate the time – Scrum master, Developer and Product owner should decide based on discussions
- Scrum master prepares a Scrum Board for tracking project activities
- Daily scrum meetings should be planned – everyone should attend without fail
- In Daily Scrum meetings – we normally take one story for the development, and design its solution. We also get updates of stories in progress, and identify-track-resolve blockers. We review the burn down chart and calculate time still required
- In sprint presentation stage – we review sprint status – basically health, discuss about areas need improvement, and changes required. We come to a agreement on how the next sprint will be run
- The Demo normally goes through product owner – and we review the feedbacks received. The comments – improvement suggestions – and additional requirements will be added in backlog after an impact analysis
As you can see, the agile way of project management is almost same as website or any web application development – but the best thing is … it keeps us happy in developing … some kind of good professional way.
No comments:
Post a Comment