Transcription

1

2

3

4

5

6

7

8

9

10 Agile (BLANK) Flow Diagram

11 The 12 Agile Principles The 12 Agile Principles are a set of guiding concepts that support project teams in implementing agile projects. Use these concepts to implement agile methodologies in your projects. 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 4. Business people and developers must work together daily throughout the project. 5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 7. Working software is the primary measure of progress. 8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 9. Continuous attention to technical excellence and good design enhances agility. 10. Simplicity the art of maximizing the amount of work not done is essential. 11. The best architectures, requirements, and designs emerge from self-organizing teams. 12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. Agile Project Management Roles It takes a cooperative team of employees to complete a project. Agile project teams are made up of many people and include the following five roles:

12 1. Development team: The group of people who do the work of creating a product. Programmers, testers, designers, writers, and anyone else who has a hands-on role in product development is a member of the development team. 2. Product owner: The person responsible for bridging the gap between the customer, business stakeholders, and the development team. The product owner is an expert on the product and the customer's needs and priorities. The product owner works with the development team daily to help clarify requirements. The product owner is sometimes called a customer representative. 3. Scrum master: The person responsible for supporting the development team, clearing organizational roadblocks, and keeping the agile process consistent. A scrum master is sometimes called a project facilitator. 4. Stakeholders: Anyone with an interest in the project. Stakeholders are not ultimately responsible for the product, but they provide input and are affected by the project's outcome. The group of stakeholders is diverse and can include people from different departments, or even different companies. 5. Agile mentor: Someone who has experience implementing agile projects and can share that experience with a project team. The agile mentor can provide valuable feedback and advice to new project teams and to project teams that want to perform at a higher level. Agile Project Management Artifacts 1. Product vision statement: An elevator pitch, or a quick summary, to communicate how your product supports the company's or organization's strategies. The vision statement must articulate the goals for the product. 2. Product backlog: The full list of what is in the scope for your project, ordered by priority. Once you have your first requirement, you have a product backlog. 3. Product roadmap: The product roadmap is a high-level view of the product requirements, with a loose time frame for when you will develop those requirements. 4. Release plan: A high-level timetable for the release of working software.

13 5. Sprint backlog: The goal, user stories, and tasks associated with the current sprint. 6. Increment: The working product functionality at the end of each sprint. Agile Project Management Events Most projects have stages. Agile projects include seven events 1. Project planning: The initial planning for your project. Project planning includes creating a product vision statement and a product roadmap, and can take place in as little time as one day. 2. Release planning: Planning the next set of product features to release and identifying an imminent product launch date around which the team can mobilize. On agile projects, you plan one release at a time. 3. Sprint: A short cycle of development, in which the team creates potentially shippable product functionality. Sprints, sometimes called iterations,typically last between one and four weeks. Sprints can last as little as one day, but should not be longer than four weeks. Sprints should remain the same length throughout the entire projects. 4. Sprint planning: A meeting at the beginning of each sprint where the scrum team commits to a sprint goal. They also identify the requirements that support this goal and will be part of the sprint, and the individual tasks it will take to complete each requirement. 5. Daily scrum: A 15-minute meeting held each day in a sprint, where development team members state what they completed the day before, what they will complete on the current day, and whether they have any roadblocks. 6. Sprint review: A meeting at the end of each sprint, introduced by the product owner, where the development team demonstrates the working product functionality it completed during the sprint. 7. Sprint retrospective: A meeting at the end of each sprint where the scrum team discusses what went well, what could change, and how to make any changes. Acceptance testing

14 Acceptance testing is a validation activity conducted to determine whether or not a system satisfies its acceptance criteria. It is the last phase of the software testing process. Agile A conceptual framework for undertaking software projects. Agile methods are a family of development processes, not a single approach to software development. Behavior Driven Development Behavior driven development (or BDD) is an agile software development technique that encourages collaboration between developers, QA and non-technical or business participants in a software project. BDD focuses on obtaining a clear understanding of desired software behavior through discussion with stakeholders. It extends TDD by writing test cases in a natural language that non-programmers can read. Bottleneck A bottleneck is a sort of congestion in a system that occurs when workload arrives at a given point more quickly than that point can handle it. It is metaphorically derived from the flowing of water through a narrow mouthed bottle where the flow of water is constrained by the size of its neck. Bugs A software bug is a problem causing a program to crash or produce invalid output. It is caused by insufficient or erroneous logic and can be an error, mistake, defect or fault. Burndown Chart A burndown chart is a visual tool for measuring and displaying progress. Visually, a burndown chart is simply a line chart representing remaining work over time. Burndown charts are used to measure the progress of an agile project at both an iteration and project level. Daily Standup/Scrum

15 A Daily Standup is a whole team meeting that happens at the same time every day that usually lasts 15 minutes or less. The meeting is designed to allow the entire team to synchronize with each other and to understand the flow and challenges of the development process. Each team member should provide the following information: what did I do yesterday, what am I planning to do today, and what impediments do I currently have? Done Also referred to as Done Done, this term is used to describe all the various tasks that need to happen before a story is considered potentially releasable. Epic A very large user story that is eventually broken down into smaller stories. Estimation The process of agreeing on a size measurement for the stories, as well as the tasks required to implement those stories, in a product backlog. Feature creep Feature creep occurs when software becomes complicated and difficult to use as a result of too many features. Kanban Kanban, pronounced /ˈkɑnˈbɑn/, is a method for developing products with an emphasis on just-in-time delivery and the optimization of flow of work on the team. It emphasizes that developers pull work from a queue, and the process, from definition of a task to its delivery to the customer, is displayed for participants to see. Lean Lean software development is a translation of Lean manufacturing and Lean IT principles and practices to the software development domain. Adapted from the Toyota Production System and is a set of techniques and principles for delivering more values with the same or less resources by eliminating waste across organizations and business processes Pair Programming

16 Pair programming is an agile software development technique in which two programmers work together at one workstation. One types in code while the other reviews each line of code as it is typed in. The person typing is called the driver. The person reviewing the code is called the observer (or navigator). The two programmers switch roles frequently. Planning Poker Also called Scrum poker, is a consensus-based technique for estimating, mostly used to estimate effort or relative size of tasks in software development. Product Backlog Acts as a repository for requirements targeted for release at some point. These are typically high level requirements with high level estimates provided by the product stakeholders. The requirements are listed on the backlog in priority order and maintained by the product owner. Product Owner The Product Owner represents the voice of the customer and is accountable for ensuring that the Team delivers value to the business. The Product Owner writes customer-centric items (typically user stories), prioritizes them, and adds them to the product backlog. Scrum teams should have one Product Owner. Retrospective A team meeting that happens at the end of every development iteration to review lessons learned and to discuss how the team can be more efficient in the future. It is based on the principles of applying the learning from the previous sprint to the upcoming sprint. Scrum Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. It is based on the adaptive and iterative methodology of software development. Scrumban Scrumban is a mix between Scrum and Kanban, which supposedly contains the best features of both methods.

17 Scrum Master Scrum is accountable for removing impediments to the ability of the team to deliver the sprint goal/deliverables. The ScrumMaster is not the team leader but acts as a buffer between the team and any distracting influences. The ScrumMaster ensures that the Scrum process is used as intended. The ScrumMaster is the enforcer of rules. A key part of the ScrumMaster s role is to protect the team and keep them focused on the tasks at hand. The role has also been referred to as servant-leader to reinforce these dual perspectives. Spike A short, time-boxed piece of research, usually technical, on a single story that is intended to provide just enough information that the team can estimate the size of the story. Sprint / Iteration A fixed duration period of time where user stories are chosen to work on. The term Sprint comes from the Scrum methodology and is analogous to the term Iteration. A sprint is defined as a 2-4 week increment of software development activities that delivers working software and the end of the increment. External influences are not allowed to change the requirements of the stories being worked on. Sprint Backlog At the beginning of each sprint, the team has sprint planning with an end result being a backlog of work that the team anticipates completing at the end of the sprint. These are the items that the team will deliver against throughout the duration of the sprint. Sprint Planning Is a pre-sprint planning meeting attended by the core agile team? During the meeting the Product Owner describes the highest priority features to the team as described on the product backlog. The team then agrees on the number of features they can accomplish in the sprint and plans out the tasks required to achieve delivery of those features. The planning group works the features into User Stories and assigns Acceptance criteria to each story. Sprint Review Each Sprint is followed by a Sprint review. During this review the software developed in the previous Sprint is reviewed and if necessary new backlog items are added.

18 Story Points Unit of estimation measuring complexity and size. Task A user story can be broken down in to one or more tasks. Tasks are estimated daily in hours (or story points) remaining by the developer working on them. Taskboard / Storyboard A wall chart with cards and sticky notes that represents all the work for in a given sprint. The notes are moved across the board to show progress. Team The Team is responsible for delivering the product. A Team is typically made up of 5 9 people with cross-functional skills who do the actual work (analyze, design, develop, test, technical communication, document, etc.). It is recommended that the Team be self-organizing and self-led, but often work with some form of project or team management. Test Driven Development Test-driven development (TDD) is a software development process that relies on the repetition of a very short development cycle: first the developer writes a failing automated test case that defines a desired improvement or new function, then produces code to pass that test and finally refactors the new code to acceptable standards. Timeboxing Timeboxing is a planning technique common in planning projects (typically for software development), where the schedule is divided into a number of separate time periods (timeboxes, normally two to six weeks long), with each part having its own deliverables, deadline and budget.

19 User Persona Personas are a description of the typical users of given software. A persona description should include: 1) Skills and background E.g. professional or beginner computer user 2) Goals E.g. what does the user expect from the product? User Story A user story is a very high-level definition of a requirement, containing just enough information so that the developers can produce a reasonable estimate of the effort to implement it. A user story is one or more sentences in the everyday or business language of the end user that captures what the user wants to achieve. A user story is also a placeholder for conversation between the users and the team. The user stories should be written by or for the customers for a software project and are their main instrument to influence the development of the software. User stories could also be written by developers to express non-functional requirements (security, performance, quality, etc.) Velocity It is a relative number which describes how much work the team can get done over a period of time. 8. Vertical Slice Showing off a feature in an application that works from start to finish but may be limited in scope. For example a rope bridge crossing a chasm is immediately useful and allows people to cross. Having that in place can help to build a better bridge later. 9. WIP Also known as Work in Progress is any work that has been started but has yet to be completed.

20 10. XP A software development methodology which is intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development, it advocates frequent "releases" in short development cycles (timeboxing), which is intended to improve productivity and introduce checkpoints where new customer requirements can be adopted. agile methods An approach to managing projects that includes an iterative workflow and incremental delivery of software in short iterations artifact A useful object created by people closing processes Formalizing acceptance of the project or project phase and ending it Efficiently kick-off meeting A meeting held at the beginning of a project so that stakeholders can meet each other, review the goals of the project, and discuss future plans process A series of actions directed toward a particular result standard Best practices for what should be done user stories Short descriptions written by customers of what they need a system to do for them

21 baseline The approved project management plan plus approved changes capitalization rate The rate used in discounting future cash flow; also called the discount rate or opportunity cost of capital cash flow Benefits minus costs or income minus expenses cost of capital The return available by investing capital elsewhere interface management Identifying and managing the points of interaction between various elements of a project internal rate of return (IRR) The discount rate that results in an NPV of zero for a project mind mapping A technique that uses branches radiating from a core idea to structure of thoughts and ideas net present value (NPV) analysis A method of calculating the expected net monetary gain or loss from a project by discounting all expected future cash inflows and outflows to the present point in time opportunities Chances to improve an organization

22 payback period The amount of time needed to recoup the total dollars invested in a project, in terms of net cash inflows project charter A document that formally recognizes the existence of a project and provides direction on the project s objectives and management return on investment (ROI) A method for determining the financial value of a project; the ROI is the result of subtracting the project costs from the benefits and then dividing by the costs SWOT analysis Analyzing Strengths, Weaknesses, Opportunities, and Threats; used to aid in strategic planning weighted scoring model A technique that provides a systematic process for selecting projects based on numerous criteria decomposition Subdividing project deliverables into smaller pieces deliverable A product, such as a report or segment of software code, produced as part of a project project scope management The processes involved in defining and controlling what work is or is not included in a project

23 project scope statement A document that includes at least a description of the project, including its overall objectives and justification, detailed descriptions of all project deliverables, and the characteristics and requirements of products and services produced as part of the project prototyping Developing a working replica of the system or some aspect of it to help define user requirements requirement A condition or capability that must be met by the project or that must be present in the product, service, or result to satisfy an agreement or other formally imposed specification requirements management plan A plan that describes how project requirements will be analyzed, documented, and managed requirements traceability matrix (RTM) A table that lists requirements, their various attributes, and the status of the requirements to ensure that all are addressed scope All the work involved in creating the products of the project and the processes used to create them scope baseline The approved project scope statement and its associated WBS and WBS Dictionary scope creep The tendency for project scope to keep getting bigger

24 scope validation Formal acceptance of the completed project deliverables top-down approach Creating a WBS by starting with the largest items of the project and breaking them into subordinate items use case modeling A process for identifying and modeling business events, who initiated them, and how the system should respond to them variance The difference between planned and actual performance Gantt Chart Advantages While there are a number of reasons to use Gantt charts below are five key reasons they are often advantageous: Avoid Completion Confusion: Gantt charts were created to keep users on track, providing a visual timeline for starting and finishing specific tasks. By providing a visual overview of milestones and other key dates, these charts are thought to offer a more understandable and memorable method of maintaining timescale-based tasks and deliverables whether tracked on a daily, weekly, monthly or yearly basis. Below diagram shows the power of visualization found in Gantt charts. In a glance you can see that the interviews are done, there 50% more to do in training etc. Keep Everyone on the Same Page: Where there is a visual framework for the work to be done, there are fewer chances for misunderstanding, especially when it comes to highly complex tasks. Using Gantt charts allow all types of stakeholders to have the same information, set mutually understood expectations, and conduct their efforts according to the desired protocol.

25 Understand Task Relationships: These charts can make clear how various tasks are interrelated and perhaps rely on the completion of another to meet specific objectives. These task relationships revolve around understanding the timing of each task, which then impacts other tasks listed. This can better assure the optimum work flow, maximized productivity and overall project success. Effectively Allocate Resources: By being able to look ahead on the Gantt chart, users can clearly discern where resources need to be anticipated, allocated or shared to maximize the use of those resources. The more closely the chart is followed, the better chance there is of keeping project costs within budget while also better assuring on-time completion. Get a Handle on the Future: While it is often easy to get caught up in day-to-day tasks as detailed on a chart, Gantt chart advantages include helping decision-makers look farther ahead to ensure each given project is working toward the achievement the organization s long-term strategic objectives. A SWOT analysis (alternatively SWOT matrix) is a structured planning method used to evaluate the strengths, weaknesses, opportunities and threats involved in a project or in a business venture. Strengths: characteristics of the business or project that give it an advantage over others. Weaknesses: characteristics that place the business or project at a disadvantage relative to others. Opportunities: elements that the project could exploit to its advantage. Threats: elements in the environment that could cause trouble for the business or project.

26 Here is a SWOT Analysis template with some examples filled in: Strengths Weaknesses Project is very complex Political support Likely to be costly Funding available May have environmental Market experience impact Strong leadership Staff resources are already stretched Opportunities Threats Project may improve local economy Environmental constraints Will improve safety Time delays Project will boost company's Opposition to change public image The SWOT analysis is a simple, albeit comprehensive strategy for identifying not only the weaknesses and threats of a plan, but also the strengths and opportunities it makes possible. While an excellent brainstorming tool, the four-cornered analysis also prompts entities to examine and execute strategies in a more balanced way. However, it is not the only factor in developing a good business strategy. "A SWOT analysis is helpful in broadly addressing questions to develop a business plan, but it doesn't go far enough," said Worthworm and SkyMall cofounder Alan Lobock. "The exercise alone won't identify your key value drivers of your business. Planning without first knowing your goals and the metrics by

27 which you will measure your progress toward achieving those goals is inefficient and misguided." Similarly, Sempurna Restoration Clinic founder Cleighton DePetro noted that a SWOT analysis is just one tool in the strategy toolbox. "When SWOT is used in conjunction with other analysis models, these frameworks for strategic thinking are well worth your time and should guide your decision making," DePetro said. Additional analytic tools to consider include PEST (Political, Economic, Social and Technological), MOST (Mission, Objective, Strategies and Tactics), or SCRS (Strategy, Current state, Requirements and Solution) analyses.