Osama Bin Gandhi Posted February 26, 2015 Report Posted February 26, 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
Fight789 Posted February 26, 2015 Report Posted February 26, 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 Team member anduru untaru in Scrum/agile room loo (PM,Dev manager, Developers team ,QA, Production managers). Every one needs to give daily status what you did yesterday and what is your task today? You need write today's task in paper and stick on wall. Developer Manager tells the stories initially. So based on his stories you need develop the code. Each story has dead line (may be 2 weeks) Please add more point here if you guys know more info
massmaharaj Posted February 26, 2015 Report Posted February 26, 2015 freshers fake petti scrum loki velthe , roju pakodi chesukoni tintaaru vallu
Osama Bin Gandhi Posted February 26, 2015 Author Report Posted February 26, 2015 what is product backlog and sprint backlong? aa terms asalu vaadthara sprint team size entha untundi? will there be a head of scrum team? Team member anduru untaru in Scrum/agile room loo (PM,Dev manager, Developers team ,QA, Production managers). Every one needs to give daily status what you did yesterday and what is your task today? You need write today's task in paper and stick on wall. Developer Manager tells the stories initially. So based on his stories you need develop the code. Each story has dead line (may be 2 weeks) Please add more point here if you guys know more info
ILAQAT_MUFLIYA Posted February 26, 2015 Report Posted February 26, 2015 what is product backlog and sprint backlong? aa terms asalu vaadthara sprint team size entha untundi? will there be a head of scrum team? Task lists
massmaharaj Posted February 26, 2015 Report Posted February 26, 2015 what is product backlog and sprint backlong? aa terms asalu vaadthara sprint team size entha untundi? will there be a head of scrum team? it is some thing like one ore more tasks if you want want to stretch or reduce the tasks based on the work that is effected
vasu21 Posted February 26, 2015 Report Posted February 26, 2015 In a Scrum meeting you can also mention if something is blocking you from performing your tasks.
massmaharaj Posted February 26, 2015 Report Posted February 26, 2015 In a Scrum meeting you can also mention if something is blocking you from performing your tasks. +11111 pani cheyakunda time pass chesevallaki or pani vere valla chetha cheyinche vallaki dabidi dibide
Osama Bin Gandhi Posted February 26, 2015 Author Report Posted February 26, 2015 cool thanks. it is some thing like one ore more tasks if you want want to stretch or reduce the tasks based on the work that is effected In a Scrum meeting you can also mention if something is blocking you from performing your tasks. +11111 pani cheyakunda time pass chesevallaki or pani vere valla chetha cheyinche vallaki dabidi dibide
ParmQ Posted February 26, 2015 Report Posted February 26, 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 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.
ParmQ Posted February 26, 2015 Report Posted February 26, 2015 what is product backlog and sprint backlong? aa terms asalu vaadthara sprint team size entha untundi? will there be a head of scrum team? Depends on the company and their requirements like required size that they need to achieve the user-story completion. normally about 6 to 8. If its too big, can be made two teams and there will be Scrum of Scrums.
massmaharaj Posted February 26, 2015 Report Posted February 26, 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. baga cheppavu
Fight789 Posted February 26, 2015 Report Posted February 26, 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. Thanks ....Good info Bro.
Osama Bin Gandhi Posted February 27, 2015 Author Report Posted February 27, 2015 Thanks for your time bro...Good info Depends on the company and their requirements like required size that they need to achieve the user-story completion. normally about 6 to 8. If its too big, can be made two teams and there will be Scrum of Scrums.
.thumb.jpg.ce42bb16ec102475a78c2087ce269c7d.jpg)
Recommended Posts