5715018
Beschreibung
Karteikarten von minal Kotwal, aktualisiert more than 1 year ago
|
Erstellt von minal Kotwal
vor mehr als 8 Jahre
|
|
| Frage | Antworten |
| Agile: * Agile is a framework for delivering products quickly and efficiently * It uses set of new practices that make product development cyclical (iterative) * It relies on lean governance (management) * It drives decision making process lower in an organisation, making that organisation responsive and adaptive * Customer in continually involved in Agile * It was created because big upfront planning stifled the development process and the contact with customer | Agile manifesto: 1. The main aim is to satisfy the customer by early and continuous delivery of product 2. Changes are welcome even in late development 3. Delivery working product frequently usually on the order of weeks 4. Build projects around motivated individuals 5. Emphasise face-to-face conversation 6. Working product is the main measure of progress 7. Continous attention to technical excellence is a must 8. Simplicity is great 9. The best designs emerge from self-organising teams |
| Scrum: * Scrum lets you bring agile to your organisation and make it work * Agile encourages communication, Scrum sets up rules for stand up meetings and how they should be concluded * Agile discusses need for iterative and incremental development, Scrum emphasises on those terms through with well-defined sprints for specific iterations * Agile suggests you track tasks with list, scrum has techniques for doing exactly that | |
| Are scrum and agile related? * Scrum is a variant of Agile * While Agile is a set of principles, Scrum puts those principles into effect with well-designed practices and techniques * Scrum is a team-based iterative and incremental Agile method for tracking projects. It has its own components such as a scrum team, backlogs, and sprints | People in Scrum: * Manages the vision - Product owner - Establishes and communicates the project vision. They achieve initial and on going funding for the project by creating the initial release plans and initial product backlog * Manage the ROI (return on investment) - Product owner- Product owner monitors the project against its ROI goals and the investment vision. They update and prioritise the backlog to make sure that the most important functionality is produced first and built upon. They prioritise and refine the product backlog and measures success against expenses |
| * Manage the development iteration - team- During the iteration the team will prioritise and develop the most important features on the product backlog first. The team expands product backlog items into more explicit tasks on a sprint backlog and then manages its own work. Self-organises around how it wants to complete the iteration. The team manages itself to its commitment | * Manage the process - Scrum Master - They are responsible for setting up the team for success by making sure the project and organisational culture is ready for meeting the ROI goals of the project. * This involves organising the sprint meeting (where product backlog is expanded into sprint backlog), a sprint review meeting (where newly developed functionality is displayed), shielding the team from any outside disturbances, holding brief daily scrum meetings, and removing any obstacles to progress |
| * Manage the release - Product Owner- They make the decisions about when to create an official release. For many reasons it may not be good to release at the end of every increment. * Similarly if an official release is planned for after the 5th increment it may be released after the 4th increment in order to respond to competitors or capture early market. * The product owner makes these decisions in a manner consistent with the investment vision that has been established for the project | next |
| What is involved? * Stories - in Scrum, the customer tells the scrum team what's needed through requirements. They are called stories. * A story is a high level definition of requirements. Containing enough info so the developer can produce reasonable estimated of the effort to implement it * The scrum team takes the supplied stories, and breaks them down into specific tasks, each of which is given a time estimate (either in story points or days/hours). These tasks are then kept track of in the sprint backlog | Backlogs: * The product backlog represents the larger picture, and lists epics, and stories for a product. * The sprint backlog is concerned with the stories and tasks that are undertaken within a sprint. The items in sprint backlogs come from the product backlog during sprint planning * Epic - larger requirement or composite user story that needs to be broken down into small segments during software development |
| Sprints: * is a development iteration. * In Scrum, you execute projects in successive iterations known as sprints * In a sprint planning session, items are taken from the product backlog and moved to the sprint backlog, based on the priority set by the product owner, and given an estimate * Sprints are intended to be 2-4 week work iterations. * At the end of the sprint, a potentially shippable product is delivered to the product owner for review | * For the product owner's part, no changes should be made to the requirements during the sprint ( changes can be introduced in the next sprint planning session) * Sprints usually start with a planning session during which the sprint backlog is created from a prioritised product backlog, and end with a end-of-sprint review, as well as delivering a product to the product owner |
| Daily scrum: * A main feature of Scrum development is the daily stand ups, called the daily scrum. * This is mandatory meeting of the scrum team and takes about 15 mins at the start of the day * The main attendees are the Scrum master, product owner can also attend. * Meeting is usually help with all people standing to literally emphasising the name of the meeting. Also giving it another name "daily stand -up" | What is expected at the Daily Scrum? Each participant is expected to answer 3 questions: 1. What did you do since the last scrum? 2. What will you do until the next scrum? 3. Do you have any roadblocks preventing you from doing your work? |
| Scrum Master: * Responsible for the process * Responsible for maximising team productivity * Sets up meetings * Conducts meetings * Representative to management * Representative to team | Product owner: * Develops and maintains the product backlog * Prioritises the product backlog * Empowered to make decisions for all customers and users * Attends sprint planning meetings and the sprint review meetings * Presents and explains product backlog to team |
| Scrum team members should exhibit the following attributes: * Experience, motivated, committed to the project full time, competent, proud of their work, able to work well with others, responsible, willing to work in teams, autonomous | next |
| Autonomy: * Scrum pushes the level of decision making downward, and its important team members feel they have the autonomy to become truly invested in the project. * Autonomy stands in contradiction to the environment from heavy governance organisations * To some extent, team members have to believe they "own" the project before they can take pride in it, commit themselves to it fully, and internalise the goals of the project | Teams: * Typically 7 to 12 people * Cross functional to all necessary tasks to be handled, e.g.: programming, , designers etc * Full time * self organising and self directed * autonomous * motivated * owns the project |
| Meetings: Sprint planning meetings: * At the start of every sprint cycle, a sprint planning meeting is held to do the following: - Select what work is to be done - Prepare the sprint backlog that details the time it will take to do that work, with the entire team - Identify and communicate how much of the work is likely to be done during the current sprint - There is usually an 8 hour limit to this meeting | Meetings: Daily scrum meeting: - All members of the development team come prepared with updates for the meeting - The meeting starts precisely on time even if some development team members are missing - Should happen at the same location same time every day - The meeting length is set to 15 mins - All are welcome, but normally only the core roles speak |
| Meetings: End meetings: - At the end of the sprint cycle, two meetings are held: the "Sprint review meeting" and the "Sprint retrospective meeting" | next |
| How to plan sprints? * Sprint planning takes place on the first day of a sprint - you plan before you start the sprint work. * Each sprint planning session lasts typically a full day, or eight hours * It consists of 2 segments. Each segment is designed to last about half a day, roughly or about 4 hours. * Those times may vary | 1. Moving items from the product backlog: - The first segment of sprint planning is focussed on selecting the high-priority items from the product backlog and moving them into the sprint backlog - and defining their sprint goals 2. Limiting the segment of the sprint planning to four hour makes sure that those 2 purposes are pursued efficiently |
| 2. Estimating backlog items - The second segment of sprint planning is all about perfecting the sprint backlog and understanding the backlog items in more detail. - This segment has 3 main purposes: 1. Team perfects the stories to be delivered 2. Team estimates the work 3. Team commits to the work and the sprint | next |
| Timesheets are tricky: - Estimating the time of the work is a hard process, but its important - Scrum depends on being efficient with time - The closer the team comes to estimating the times the better it will be - A preferred approach of time estimating is to use story points in scrum teams | Story points and planning poker: - A story point is a unit of time-wrok that can be assigned to each task. - Typically, its one day of work for one person, but its adaptable - Most organisations use relative sizing to decide story points - In a process called planning poker, the team members estimate the story point of each story or task. That assigns a specific amount of work and time per task. |
| When estimating story points team members should consider: - How many story points did they deliver last sprint? This helps set a baseline of how much work can be done in this sprint - Are there any holidays planned for the coming sprint? This adjusts the total points a team can complete in a sprint - Are there any big milestone/events taking place that affect the process? This may impact the amount of work that can be delivered | Sprint velocity: - The team then considers a sprint velocity target - The sprint velocity is the time it will take to complete the sprint, and gives an indication of the team's development capacity - It very helpful to look at team's previous sprints velocity when planning the current sprint's velocity - Each task is estimated for time, typically in story points, util the potential velocity is reached - Usually the team will start will highest priority stories and tasks first, estimating the time they will take, and then continue with the lower-priority stories and tasks |
Möchten Sie mit GoConqr kostenlos Ihre eigenen Karteikarten erstellen? Mehr erfahren.