Mukund hasn't listed a bio yet.
Sr Programmer Analyst at Autodesk
San Rafael, California 94941
Designation - Sr SAP Programmer Analyst at Autodesk Inc. Role - Scrum Master/Individual contributor Feb '2011 - till present(this project is full time) Objective : The objective of this project is to build a scalable, eCommerce platform that will allow the company to reach new customers, expand the types of products and services being offered. This platform is built as an integrated store that has connectivity with backend ERP system and will replace the existing standalone store that has no connectivity with backend. Scope: The scope of this project includes building the eStore platform for one geo and expanding the functionality to other geos.The project is implemented using Agile Scrum Methodology. The team consists of a Product Owner, a Scrum Master, a business analyst, 3 developers and 2 testers. The duration of the Sprint is 2 weeks. During the first day of the Sprint, the product owner picks up the stories from backlog which provide key business value and paste them on Task board in the order in which they should be worked on by scrum team. The team comes to an agreement on how many stories can be considered in current sprint based on their Story Points and reviews them with product owner. Now, the team picks up each story and writes down the tasks relevant to burn the story. "Done" criteria will be used to burn a story that normally includes code changes, unit and integration testing, test case documentation and business acceptance from product owner. On the last day of Sprint, a demo will be arranged by team for all the key stakeholders to show the work completed by team using working software and answers their questions. After the demo, team will do a "Retrospective" meeting where they review accomplishments, challenges and areas of improvement. At this point, the stakeholders review their business decisions with the work completed in the last sprint and provides feedback to Product owner besides giving him/her the inputs on priorities that have changed. Based on the changing priorities or input from business stakeholders, product owner will chose the next set of stories to be worked on in following sprint. In this way, the team keeps delivering the value to business in incremental steps so that the work accomlished will be aligned to business priority. The Scrum master will ensure that the team completes the stories without any impediments and facilities any discussions and meetings that are required for the team. The mandatory meetings in every sprint include Daily Stand up(for 15 minutes), backglog grooming, Sprint Review(Demo) and Sprint Retrospective. All the stories along with their tasks are pasted on a task board in 3 columns "To Do", "Doing" and "Done". During the daily stand up meeting, every team member gives an update on what they did the previous day, what they plan for current day and impediments, if any. As the tasks get completed, they will be moved from "To Do" to "Doing" to "Done". The team uses a "Burn Up" and "Burn Down" charts in every sprints to keep track of how many points have been completed till date and how many points are still left to be completed. As more stories come up in backlog, there will be a planning poker session to estimate the story points for every story based on their relative complexity with other stories. In backlog grooming session, the stories will be refined by the team in discussion with Product owner. Deliverables : The key deliverables include design documents, working software, technical documentation, test case results, knowledge transfer to support teams, performance test result, automation scripts etc. Outcome : The outcome of this project is an integration eStore platform which provides technolgy foundation and expanding this platform to various geographical regions to meet the functionality of respective business processes. Till date I have worked on close to 335 days excluding holidays and vacations(working 5 days a week on this scrum project). Working for 8 hours a day bring the numbers of hours spent on Agile related work to 2680 hours.
No recent activity