Hyderabad_Nawab Posted February 27, 2015 Report Posted February 27, 2015 I am writing at very high level. Less than half-of what we followed. Roles : Product owner - One we all bend in front of Scrum master - one who makes all team members bend Developers, testers and etc- Who that bend Meetings - sprint planning, Daily standup, sprint retrospective Product owner - Business cases ni dissect chesi (single testable functionality in terms of the business) oka log maintain chesthaadu. Adhe product backlog. He prioritize that based on the business value. At the begining of the each Sprint (During the sprint planning meeting) he puts them in front of the whole team based on the priority. Scrum master arranges the team. All the developers will chalk out things like effort estimations and etc (can use poker planning for this). Based on the team capacity (team availability and the effort points), the whole team will pick up some X number and agree to commit for the Sprint (can be 2 or 3 weeks based on the team agreement with the product owners). The developers and testers can dissect the user-stories further into tasks and work on them. The user stories that we committed to product owner during the sprint planning meeting will into sprint backlog which is the one hangs on the Scrum board based on the priority. The team members will take one by one as per the priority and start work on that. Scrum master daily conducts the daily stand-ups and finds out for each user - story that is in the state of work in progress (WIP) and understand how much the team has finished each day and estimates the number of effort points the team has burned and relay on the burn-down charts to understand the velocity of the team and how they are doing. And he tries to understand if there are any blocker for each user-story that is impeding the user-story to be completed and he tries to remove those blockers The sole aim of Scrum master and every one in the team is to deliver what was committed during the sprint planning meeting based on the team capacity. Just before the Sprint closing, team will gather and retrospect about the things like ..+ves, -ves, things that wanted to continue and things that the team want to discard and etc. Its the cycle and will move until all the user-stories from the product backlog have been completed. To achieve the the goal of providing the best to the product owner..different engineering practices are employed to improve the non-functional requirements. Thats another big thing to write. GP... Ivi Actual Rules that will not be Followed Anuko..
ParmQ Posted February 27, 2015 Report Posted February 27, 2015 GP... Ivi Actual Rules that will not be Followed Anuko.. Yeah, true. Memu oka project lo use chesam. Ikkada nenu raasina dhanikante..chala ekkuve use chesam. Inko project lo ikkada rasindhi use chesam..migilinavi bisket
k2s Posted February 27, 2015 Report Posted February 27, 2015 I am writing at very high level. Less than half-of what we followed. Roles : Product owner - One we all bend in front of Scrum master - one who makes all team members bend Developers, testers and etc- Who that bend Meetings - sprint planning, Daily standup, sprint retrospective Product owner - Business cases ni dissect chesi (single testable functionality in terms of the business) oka log maintain chesthaadu. Adhe product backlog. He prioritize that based on the business value. At the begining of the each Sprint (During the sprint planning meeting) he puts them in front of the whole team based on the priority. Scrum master arranges the team. All the developers will chalk out things like effort estimations and etc (can use poker planning for this). Based on the team capacity (team availability and the effort points), the whole team will pick up some X number and agree to commit for the Sprint (can be 2 or 3 weeks based on the team agreement with the product owners). The developers and testers can dissect the user-stories further into tasks and work on them. The user stories that we committed to product owner during the sprint planning meeting will into sprint backlog which is the one hangs on the Scrum board based on the priority. The team members will take one by one as per the priority and start work on that. Scrum master daily conducts the daily stand-ups and finds out for each user - story that is in the state of work in progress (WIP) and understand how much the team has finished each day and estimates the number of effort points the team has burned and relay on the burn-down charts to understand the velocity of the team and how they are doing. And he tries to understand if there are any blocker for each user-story that is impeding the user-story to be completed and he tries to remove those blockers The sole aim of Scrum master and every one in the team is to deliver what was committed during the sprint planning meeting based on the team capacity. Just before the Sprint closing, team will gather and retrospect about the things like ..+ves, -ves, things that wanted to continue and things that the team want to discard and etc. Its the cycle and will move until all the user-stories from the product backlog have been completed. To achieve the the goal of providing the best to the product owner..different engineering practices are employed to improve the non-functional requirements. Thats another big thing to write. Nice....
The Warrior Posted February 27, 2015 Report Posted February 27, 2015 I am writing at very high level. Less than half-of what we followed. Roles : Product owner - One we all bend in front of Scrum master - one who makes all team members bend Developers, testers and etc- Who that bend Meetings - sprint planning, Daily standup, sprint retrospective Product owner - Business cases ni dissect chesi (single testable functionality in terms of the business) oka log maintain chesthaadu. Adhe product backlog. He prioritize that based on the business value. At the begining of the each Sprint (During the sprint planning meeting) he puts them in front of the whole team based on the priority. Scrum master arranges the team. All the developers will chalk out things like effort estimations and etc (can use poker planning for this). Based on the team capacity (team availability and the effort points), the whole team will pick up some X number and agree to commit for the Sprint (can be 2 or 3 weeks based on the team agreement with the product owners). The developers and testers can dissect the user-stories further into tasks and work on them. The user stories that we committed to product owner during the sprint planning meeting will into sprint backlog which is the one hangs on the Scrum board based on the priority. The team members will take one by one as per the priority and start work on that. Scrum master daily conducts the daily stand-ups and finds out for each user - story that is in the state of work in progress (WIP) and understand how much the team has finished each day and estimates the number of effort points the team has burned and relay on the burn-down charts to understand the velocity of the team and how they are doing. And he tries to understand if there are any blocker for each user-story that is impeding the user-story to be completed and he tries to remove those blockers The sole aim of Scrum master and every one in the team is to deliver what was committed during the sprint planning meeting based on the team capacity. Just before the Sprint closing, team will gather and retrospect about the things like ..+ves, -ves, things that wanted to continue and things that the team want to discard and etc. Its the cycle and will move until all the user-stories from the product backlog have been completed. To achieve the the goal of providing the best to the product owner..different engineering practices are employed to improve the non-functional requirements. Thats another big thing to write. Nice post
The Warrior Posted February 27, 2015 Report Posted February 27, 2015 lol lol emundi... project lu cheyymani adagamantavaa
Diana Posted February 28, 2015 Report Posted February 28, 2015 Agile Scrum stage wise em chestaro koddiga cheppandi...want to know what exactly is done in real time.Thanks also commonly used words kooda cheppandi..like sprint time, sprint size etc e peru cheppi every 2 weeks or 4 weeks release petti mental peace lekunda chestaru :police:
libraguy863 Posted February 28, 2015 Report Posted February 28, 2015 Scrum agile lo everyday task update ivvali wtz today work wt you did yesterday wtz its status complete or pending ani. Sprint planning lo Motham team will gather around and discuss the tasks BA task 1 dev task 1 QA task 1 ala Meaning BA finishes the req and dev picks the dev and QA does the testing. All are put on a wall with stickies Sometimes tasks are dependent on one another like dev taking long time so QA can put it in back long or move to next sprint. Sprint is 4 weeks long 140-160 hrs and we report to scrum master who will send our status updates to PM and he will report to product owner the project financer
.thumb.jpg.ce42bb16ec102475a78c2087ce269c7d.jpg)
Recommended Posts