...User Stories Guide What are they? User stories are value-focused units of delivery that are typically used in Agile projects. Written from the customer or stakeholder’s perspective, user stories share what is needed and why. The “who” in a user story is typically someone with a particular role or title, or it could be from the perspective of a persona: a fictitious, sample user’s behaviors and needs, spelled out in detail. When choosing the “who”, avoid being too general (e.g. “As a user...”) which defeats the purpose of pinpointing the value for your target audience. Write all stories with the “who” included, even those stories that are very technical. Template The user story template is designed to help Product Owners and others tell stories with a clear “who”, “what” and “why”. As a registered user, I want to reset my password, so that I can get back into the site if I forget my password. As an unregistered user, I can sign up for the site, so that I’m able to have a personalized experience. As Tom, I want to only see updates from close friends, so that I can view relevant updates during my time online. As wh o, I want what, so that why. Who? Another Template Some stories benefit from more than one “who”. In those cases, you might want to include multiple who-why pairs. what: Track history of which products registered shoppers have viewed. who: Registered Shoppers why: So I can go back and find again (and buy) what I’ve previously researched who: Marketing why:...
Words: 666 - Pages: 3
...Group5? Sprint 1 Garage for tractor. Positive Splitting the user story into tasks and splitting the tasks between people went well and everyone had opportunity to participate. However we never really did it in a more organized way. we had communication with the team building the tractor to decide the size of the garage (however it was not enough and we didn’t notice them changing the size). Negative Went in blind, no clear idea how large anything was supposed to be. No-one had picked the actual tractor by the time we picked the garage. Maybe we should have, as it was higher on the priority. Lead to wrong size of tractor supplied by the other group and a way too large garage in reply. Too high velocity planned, didn’t take fetching parts into the account, which took longer than expected due to all the people. It also took time to organize people and to figure out scale of buildings Sprint 2 Re-done garage and canoes. Positive Lower velocity to 15 from 20 lead to us being able to rebuild the garage (13pts) and add in the small user story for canoes as well (2pts). Also because a member disappeared We did not accept new requirements during the sprint. Might have been more due to being irritated than knowing what we were doing. Communication in the group worked very well and splitting up the tasks was fast. As we had already collected the needed parts in the last sprint we didn’t have to spend as much time on that. Except for the canoes. Communicated with Product...
Words: 794 - Pages: 4
...Real Time Narsi Saturday, December 26, 2015 QA quality Assurance ; time n budget; quality assurance n quality control are diff,Assurance involves all dev process.; quali control is testing. Assurances monitor standards and procedures. 12:08 PM SRS/FRS/BRS Software/Functional/Business requirements specification Tester: Designing test cases, Set up, execute , evaluating n recovering tests n errors. Func testers/black box testers SDLC software/system devp life cycle Req analy, design, deve, testing, implementation, maint. UML Unified Modling lang.- rep the flow Use Case pictorial rep.-req doc BA interacts with clients n customers and gather req and analyze. BRD business req docu. Build a combo of programs. Defect Lifecycle. Test summary report is one of the deliverables like test results, bulk rep,test reports. Water fall WFM and agile AM- adv and dis adv; Comparison Requirement analysis tester role starts. Daily standup meeting Agile- Scrum Do not leave anything untested. Waterfall it doesn’t go back Test to break attitude, Diplomatic, think as a customer, strong desire for quality, should know about the software, attention to detail, good relations with technical and non tech ppl, Sprint Sprint Sprint Sprint BBT input and output WBT internal. Prct planning Req ana Dev Testing Implementation Sprint: Time frame Scrum master Proi based on prjct ownr. Last Part Audio recording started: 6:02 PM Saturday,...
Words: 548 - Pages: 3
...is also necessary to validate that all the critical training has been provided for the operation of the equipment or process. There are a number of tests and checks required when executing the installation qualification protocol and they are as follow: 1) Examining the equipment or process design. This involves documenting all the hardware systems supplied with regards to the model and serial numbers whilst performing visual checks on all of the equipment. Checking the supplied software, referencing and documenting the program number and title, the version number and last date modified. Also checking the back up software and documentation supplied. The key documents that would need to be referenced for these checks are the User Requirements specifications, the Functional specification and the design qualification. 2) The examination of material certifications for any parts coming into direct contact with the product being produced. Involves examining the materials of construction list and lubricant list to identify and obtain the required material certifications. Identifying any important elements of...
Words: 1134 - Pages: 5
...coders/ testers at Infosys. This means, you are expected to do a lot of domain trainings. I have done many in the past and tell you what – the experience has been good. As a trainer you need to do your homework properly and be up-to-date in your chosen domain. Presales is another stream. As a presales anchor at Offshore – you should be able to handle Client Visits and lend Proposal support. This involves market research/ deck preparation. A deck is a suite of inputs – Value proposition of services, staffing plan, costing etc. As a presales anchor at onsite (or locations abroad), you can be projected as a BDM, and you literally get to acquire clients. Apart from this, one can be into Delivery. In delivery, you would be expected to carry out user acceptance testing, suggest improvements to the project has been managed and services have been offered to clients. Also, one has to review test cases, even do testing (depends on your luck – manual/automation/performance are the possibilities) Requirements gathering is yet another path that a BA gets to traverse. A requirements analyst – engineers requirements, gathers and documents them. You get to due-diligence of clients’ applications and interface with them to understand their requirements better. These are some of the streams that I am able to think of Will add more as and when I recollect..Hope this is...
Words: 255 - Pages: 2
...[pic] ADVANCED SYSTEK PVT. LIMITED. 299/300, GIDC,BEHIND NOVINO BATTERY, MAKARPURA, BARODA – 390010,INDIA. SITE ACCEPTANCE TEST FOR ELECTRONIC FLOW METER – IOCL ITARSI CUSTOMER: INDIAN OIL CORPORATION LIMITED, MPSO END USER: INDIAN OIL CORPORATION LIMITED, ITARSI PURCHASE ORDER: 23375955 DATED 10th MAY 2011 Doc No.: IOCL/ITARSI/ASPL/9472/SAT/REV 01 |REVISION |DATE |PREPARED BY |CHECKED BY |APPROVED BY |REMARKS | |SIGNATURE | | | | | | |CONTENTS SHEET | |SL. NO. |DESCRIPTION |PAGE NOS. | | |INTRODUCTION |2 – 5 | | |SYSTEM CHECKS |6 - 7 | | |LOADING OPERATION |8 - 10 | | |Local Loading Interruption...
Words: 995 - Pages: 4
...| | |Mohit Kasana | |Contact No: +91 - 9029070090 | |E-mail: kasana221286@gmail.com | | | Career Objective: To take a challenging post for understanding business change needs, assessing the impact of those changes, capturing, analyzing and documenting requirements and then supporting the communication and delivery of those requirements with relevant parties. Professional summary: ✓ 2.8 years of experience in the field of IT on as Functional Consultant Oracle Applications ERP and Business Analyst for Bespoke Applications. ✓ Extensive experience in Requirement gathering, Analysis and understanding of AS-IS and TO-BE models, Documentation (like BRD’s, Wireframes, Use cases, Test cases, and Test Plans) and High Level Design. ...
Words: 805 - Pages: 4
...Guidelines for Creating a Statement of Work Statement of Work Defined The Statement of Work (SOW) describes the specific requirements applicable to a particular item or service being purchased. The SOW details the services a Supplier shall perform, indicating the type, specification, level, and quality of goods and/or services, as well as the Supplier’s time schedule for performance. Roles for Developing the SOW Document Customer (End-User, Requestor) The Customers focus should be on defining: • What the SOW is expected to achieve? • What constitutes an acceptable deliverable? • When deliverables are due? • How are deliverables expected to be produced and provided? Buyer The Buyer’s primary role is to: • Consult and advise the Customer on how to structure Deliverables, Acceptance Criteria, and Tasks in a manner most likely to result in an effective contractual agreement, and to • Finalize the SOW document (incorporating Customer-generated content) in a format consistent with University standards. Steps for Writing the SOW 1. Provide background on the requirement, including the objective or purpose. Consider citing funding source information, historical precedent, or parallel sourcing efforts that provide additional information on your requirement. 2. Define the requirement and/or the services to be provided. 3. List the specific tasks to be performed by Supplier. • Categorize tasks as either...
Words: 529 - Pages: 3
...Q1. Is CIMS a good idea for WRPS? Why or why not? Waterloo Regional Police Service (WRPS) was working with seven other police services organizations on the Common Information Management Systems (CIMS) project. The main objective of CIMS project was to share information between the police services organizations to identify crime trends and to operate in an informed and proactive manner. CIMS was an extension/expansion of earlier police information systems and it was third upgrade of the systems for WRPS. The problems started from the beginning when the project started in 1998 and they were not able to identify any Vendor during the first RFP project who could satisfactorily meet stringent system integration requirements. Only one vendor named Integrated Technologies Group (ITG) submitted the proposal in the 2nd round of RFP after simplifying the system integration requirements. ITG was based in mid-Atlantic U.S. This is clearly a sign that CIMS was a very complex project and all vendors except ITG felt that they could not meet the requirement and did not even submit an RFP whereas, ITG received a solid score based on the Statement of Work and appeared to be able to deliver the level of required systems integration. Chief Gravill had a solid educational background and long history of his involvement with Information Systems. I am not sure if other Police services organizations had similar type of leaders and level of commitment on this project. The issues started to surface...
Words: 589 - Pages: 3
...1. In the Scrum Guide reading for this week, there are3 separate roles defined for the Scrum team, the Product Owner, the Development team and the Scrum Master. Of the three roles, which one is closest to the role of the traditional project manager describing why this is the best fit (1a) and why the other two are not (1b). (1a) According to the Scrum Guide reading, I think the product owner is the closet to the role of the traditional project manager due to the fact that the traditional project manager is responsible to organize in order to archive project's success, and meet the project requirements. A person who plays this role has to develop team members and work with stakeholders for setting and managing their expectations. However, the product owner is a person who is responsible for a success of scrum in order to maximize the work of the development team and the value of the product. The product owner is also responsible to ensure that team members understand all project requirements by creating the product backlog, and ensure that a project will get done on time within limited budget. (1b) There are many reasons that the development team and the scrum master are not similar to the traditional project manager. To begin with, the development team is a cross-functional team, which is responsible for developing the product. In a group, members may consist of people who have different skills as a team needed such as developers, tester, business analysts, and so on...
Words: 440 - Pages: 2
...Subsea Ver. 05 Status Re-issued Constr Issue date 2012.09.19 KENJURA, RICHARD Made by KENJURA, RICHARD Checked by NGUYEN, ROSEMARY Approved by KENJURA, RICHARD Originator: SDRL - UNIVERSAL PARTS C OF C , MTRS , COATING 10000836331-PDC-000 This document contains Aker Subsea legal entity proprietary and confidential information that is legally privileged and is intended only for the person or entity to which it is addressed and any unauthorised use is strictly prohibited. It is provided for limited purpose and shall not be reproduced, stored electronically, transferred to other documents, disseminated or disclosed to any third parties without the prior written consent of the relevant Aker Subsea legal entity. Any attachments are subject to the specific restrictions and confidentiality regulations stated therein and shall be treated accordingly. The document is to be returned upon request and in all events upon completion of use for which it was provided. Document: SDRL - UNIVERSAL PARTS C OF C , MTRS , COATING Version: Issue date: Page: 10000836331-PDC-000 05 - Re-issued Constr 2012.09.19 2 of 6 TABLE OF CONTENTS 1. 1.1. 1.2. 2. 3. 3.1. 3.2. 3.3. 3.4. 4. 5. 5.1. 5.2. INTRODUCTION ............................................................................................................................. 3 Purpose............................................................................................................................................ 3 Scope...
Words: 1142 - Pages: 5
...Software Development Life Cycle is a process that ensures good software is built. Each phase in the life cycle has its own process and deliverables that feed into the next phase. There are typically 5 phases starting with the analysis and requirements gathering and ending with the implementation. Let’s look in greater detail at each phase: Requirements Gathering/Analysis This phase is critical to the success of the project. Expectations (whether of a client or your team) need to be fleshed out in great detail and documented. This is an iterative process with much communication taking place between stakeholders, end users and the project team. The following techniques can be used to gather requirements: * Identify and capture stakeholder requirements using customer interviews and surveys. * Build multiple use cases to describe each action that a user will take in the new system. * Prototypes can be built to show the client what the end product will look like. Tools like Omnigraffle, HotGloo and Balsalmiq are great for this part of the process. In a corporate setting, this means taking a look at your customers, figuring out what they want, and then designing what a successful outcome would look like in a new bit of software. Design Technical design requirements are prepared in this phase by lead development staff that can include architects and lead developers. The Business Requirements are used to define how the application will be written. Technical requirements...
Words: 917 - Pages: 4
...CIS 517 ASSIGNMENT 2 WATERFALL AND AGILE To purchase this visit here: http://www.activitymode.com/product/cis-517-assignment-2-waterfall-and-agile/ Contact us at: SUPPORT@ACTIVITYMODE.COM CIS 517 ASSIGNMENT 2 WATERFALL AND AGILE Research agile methodologies including SCRUM and extreme programming (XP). Write a two to three (2-3) page paper in which you: Explain waterfall methodologies and identify their relationship to the PMBOK® process groups. Explain agile methodologies and identify their relationship to the PMBOK® process groups. Analyze the need for waterfall and agile methodologies. Explain the advantages of extreme programming (XP) and analyze the advantages of its application in high-budget short-time projects. Explain the factors to consider when selecting a project management methodology (Waterfall vs Agile). Use at least two (2) quality resources in this assignment. Note: Wikipedia and similar Websites do not qualify as quality resources. Your assignment must follow these formatting requirements: Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions. Include a cover page containing the title of the assignment, the student’s name, the professor’s name, the course title, and the date. The cover page and the reference page are not included in the required assignment page...
Words: 760 - Pages: 4
...Riordan Business-to-Business Web Site Use Case Scenarios Analysis In deciding which way to take Riordan Manufacturing’s business-to-business web site use case studies were performed and the top two scenarios were chosen for further analysis. Both scenarios present a way for Riordan to improve raw material ordering through different means. In order to decide which path to take the two scenarios will be discussed in greater detail including a brief synopsis on the technological role involving systems analysis and design, database design, programming, networking, and the web. Use Case 1 As described before, in use case scenario 1, a Riordan employee would log into a business-to-business web site and place an order with one of our partnered vendors as Figure 1 depicts. The employee logs into the secure website, chooses a vendor from a list, selects from the common list of products purchased from the vendor, chooses a quantity and enters a required by date, the vendor receives notification of an order, verifies credit status or requests credit card information, fills the order, generates an invoice, and ships the order to our warehouse. Use Case 2 In use case scenario 2, as shown in Figure 2, the approach to replenishing key inventory levels resides with the vendor. Triggers in the database alert the vendor via email that the level is at its threshold and then the supplier logs into the secure business-to-business web site, issues an order to ship replenishment supplies...
Words: 795 - Pages: 4
...Human Resources, who is Yvonne McMillan should also be interviewed for her requirements and how does she see what is needed for connectivity to all other business locations using a new Information System. Asking any and all employees who use the current system the company has and what improvements can be done. All of these individuals information is a way of gathering information for this service request. Information Gathering Techniques The primary information gathering technique will be as a proposal to use the Use Case method. A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. The use case is made up of a set of possible sequences of interactions between systems and users in a particular environment...
Words: 1089 - Pages: 5