Recomendados
Mais conteúdo relacionado
Semelhante a presentation (1)
Semelhante a presentation (1) (20)
presentation (1)
- 1. 1 Intern Project Presentation Maryam Bacchus Lowe’s Digital Summer 2016
- 2. Lowe’s Digital 2 Introduction School: Purdue University, Senior Major: Computer Graphics Technology Minors: Information Technology, Spanish Clubs/Activities: AIESEC, Women in Technology, UNICEF, Painting/Drawing Position at Lowe’s: Business Analyst, 7th floor
- 3. Lowe’s Digital 3 Agenda Agile Environment Continuous Improvement of Lowes.com Redesign Validation Form for Mobile Lessons Learned
- 4. Lowe’s Digital 4 Agile Environment I. The concept II. How it works III. Advantages & Disadvantages IV. 7th floor work environment
- 5. Lowe’s Digital 5 Lowes.com Redesign Continuous Improvements I. Objective of redesign a. Improved omni-channel experience b. Updated design c. Usability d. Changes and releases processed faster II. Hypercare and Continuous Improvement after Launch a. Sources for feedback b. Hypercare – Warranty time c. CI Enhancements
- 6. Lowe’s Digital 6 BA Redesign Work I. Writing stories and acceptance criteria a. End-user perspective b. Type of user, what they want, why c. “Conditions of satisfaction” d. Solution vs. Intent II. Timeline of a story life a. Desired functionality intake/ticket b. BA story c. Review (Quad – QA, Tech lead, PO, BA) d. Development e. QA tests f. Business approval
- 10. Lowe’s Digital 10 BA Role in Best Practices - Mobile I. Providing effective documentation II. Form validation for Android III. Synching with iOS criteria IV. Discovered inconsistencies V. Streamline further development of applications
- 11. Lowe’s Digital 11 Validation Form - Android Lacking requirements
- 12. Lowe’s Digital 12 Lessons Learned I. Etiquette of a corporate environment and productivity II. The BA role and responsibilities III. Take advantage of opportunity IV. Be comfortable being uncomfortable
- 13. Lowe’s Digital 13 Last Words “Be curious, ask questions, follow your passions." ~ Gihad Jawhar, VP Digital, Interviewee "Onix I choose you!" ~Brock Allender, Senior IT BA, (Brock Harrison) “Work hard, play hard.” ~Ryan Barto, Senior Associate IT BA, Mentor/Ninja "Focus on your strengths and the things that engage you the most." ~Todd Borgmeier, Manager IT BA, Manager/Gangster
- 14. Lowe’s D I G I T A L 14 Q&A
Notas do Editor
- To set the context of my work environment, I would like to first introduce the methodology in which the seventh floor and a few other projects are run on. Waterfall, a methodology commonly practiced in the digital realm is the sequential design process many teams utilize in the digital space.This means that as each of the eight stages (conception, initiation, analysis, design, construction, testing, implementation, and maintenance) are completed, the developers move on to the next step. The advantages include that the client knows what to expect. They’ll have an idea of the size, cost, and timeline for the project. They’ll have a definite idea of what their program will do in the end. However my work environment was in agile where work for a project is broken into modules, which were completed in weekly or monthly sprints, and at the end of each sprint, project priorities are evaluated and tests are run. These sprints allow for bugs to be discovered, and customer feedback to be incorporated into the design before the next sprint is run. Standups Collaboration at every stage Make the time delivery dates – time budget Disadvantages of waterfall in .com – this application will most likely have many changes, interactive with millions of people, changes will be necessary constantly, customers will want to use application differently than intended Validate with different browsers and platforms All new devices (wearables) 1. The Agile methodology allows for changes to be made after the initial planning. Re-writes to the the program, as the client decides to make changes, are expected. 2. Because the Agile methodology allows you to make changes, it’s easier to add features that will keep you up to date with the latest developments in your industry. 3. At the end of each sprint, project priorities are evaluated. This allows clients to add their feedback so that they ultimately get the product they desire. Tough for a large corporation to be agile
- (OBJECTIVE) Redesign of Lowes.com Intent was to give customers a better experience on the site Site hadn't been updated in 5/7 years Better usability Modernizing Design using simplistic principle From a tech standpoint, changes and releases are processed faster (easy to iterate) Omni-channel experience for customers Hypercare and Continuous Improvement after launch Measuring customer usage and adjusting site accordingly Stories come from Feedback customer interaction Foresee Looking at numbers around sales Hypercare - warranty time (how long it takes to fix something broken) - defects - priority CI - new enhancements necessary for customer interaction experience Kanban - continued until resources decline Kanban is you work on one thing at a time until you run out of time/money, unlike traditional agile with sprints
- Stories A user story is a tool used in Agile software development to capture a description of a software feature from an end-user perspective. The user story describes the type of user, what they want and why. A user story helps to create a simplified description of a requirement Acceptance criteria: Acceptance Criteria are a set of statements, each with a clear pass/fail result, that specify both functional (e.g., minimal marketable functionality) and non-functional (e.g., minimal quality) requirements applicable at the current stage of project integration. These requirements represent “conditions of satisfaction.” There is no partial acceptance: either a criterion is met or it is not Do not state solution, state intent Meetings with the business (product owners, stakeholders), developers, testers Error/enhancement to be made > intake/ticket > BA writes story/acceptance criteria > Review it with leads (Quad - QA, Tech lead, PO, and BA) > Review with implementation team > *BA work done* > developer starts working on it > Testers test > business approves product Please let me know if you get stuck on something, please tell me if you need a more clear explanation Speak about timeframe (one afternoon to finish a story opposed to two weeks in waterfall, sometimes things go from inception to production in two days)
- Example of stories - Show the screenshot of the backlog in general of jira At first tens of tickets a day Then customers adjusted more Acceptance criteria Goes to the ready board after this
- To put things into perspective, and make it easier to understand
- Form validation for Android App Inconsistencies within forms in the android lowe's app Same fields may have had different requirements (character count) Never documented in a central location entirely (for easy access by team) Moving forward, used for reference for continuous improvement items added Synching with iOS criteria Adding consistency to further development of applications In addition to typical BA work, part of the BA role is to provide documentation that helps improve effectiveness of the agile team (can be referenced by anyone on the team) Show validation form
- Going through the application and documenting fields for every form exposed areas in need of improvement or stronger criteria in order to create consistency across the app and furthermore to the next updates and iOS. Recommendations arose from the missing criteria and realizing where inconsistencies may occur
- Holding my first criteria meeting alone, where criticism is often present and things get changed a lot, but it was satisfying taking things into my own hands and seeing something come of it
- Takeaways from everyone and internship in general