Создание бэклога продукта с помощью карты бизнес-эффектов (Impact Map)Artem Serdyuk
В слайдкасте на примере рассмотрена генерация бэклога продукта с помощью карт бизнес-эффектов (Impact maps) и расстановка приоритетов с использованием бизнес-взвешивания (Business Weighting)
Arlen Bankston
Arlen is an established leader in the application and evolution of process management methodologies such as Lean, Six Sigma and BPM, as well as Agile software development processes such as Extreme Programming (XP) and Scrum. He is a Lean Six Sigma Master Black Belt and Certified ScrumMaster Trainer. He also has twelve years of experience in product design, leveraging principles of information architecture, interaction design and usability to develop innovative products that meet customers’ expressed and unspoken needs. Arlen has led Agile and Lean deployment and managed process improvement projects at clients such as Capital One, T. Rowe Price, Freddie Mac, and the Armed Forces Benefits Association. Arlen’s recent work has centered on combining Lean Six Sigma process improvement methods with Agile execution to dramatically improve both the speed and quality of business results. He has also led the integration of interaction design and usability practices into Agile methodologies, presenting and training frequently at both industry conferences and to Fortune 100 clients.
Creating a backlog of user stories is pretty straight forward but it doesn't help you when it comes to decisions like what to build first, how to prioritize and groom the backlog, how to scope and plan the project, and how to visualize progress. The traditional backlog is simply too flat and often too long to help you see the bigger picture and make good decisions. User Story Mapping helps simplify all of these common project issues. By adding a third dimension to your backlog, your team will make better decisions about priorities, scope, and planning while improving your ability to visualize progress.
In this practical session I’ll cover the basics of user story mapping before walking you through case studies of how our teams are using this approach and the results we are achieving. I'll show you the before, during, and after pictures from several projects so that you can understand how our maps progress during the projects and how we use them to influence iterative development, promote good decision making, and visualize priorities, plans, scope and progress.
Создание бэклога продукта с помощью карты бизнес-эффектов (Impact Map)Artem Serdyuk
В слайдкасте на примере рассмотрена генерация бэклога продукта с помощью карт бизнес-эффектов (Impact maps) и расстановка приоритетов с использованием бизнес-взвешивания (Business Weighting)
Arlen Bankston
Arlen is an established leader in the application and evolution of process management methodologies such as Lean, Six Sigma and BPM, as well as Agile software development processes such as Extreme Programming (XP) and Scrum. He is a Lean Six Sigma Master Black Belt and Certified ScrumMaster Trainer. He also has twelve years of experience in product design, leveraging principles of information architecture, interaction design and usability to develop innovative products that meet customers’ expressed and unspoken needs. Arlen has led Agile and Lean deployment and managed process improvement projects at clients such as Capital One, T. Rowe Price, Freddie Mac, and the Armed Forces Benefits Association. Arlen’s recent work has centered on combining Lean Six Sigma process improvement methods with Agile execution to dramatically improve both the speed and quality of business results. He has also led the integration of interaction design and usability practices into Agile methodologies, presenting and training frequently at both industry conferences and to Fortune 100 clients.
Creating a backlog of user stories is pretty straight forward but it doesn't help you when it comes to decisions like what to build first, how to prioritize and groom the backlog, how to scope and plan the project, and how to visualize progress. The traditional backlog is simply too flat and often too long to help you see the bigger picture and make good decisions. User Story Mapping helps simplify all of these common project issues. By adding a third dimension to your backlog, your team will make better decisions about priorities, scope, and planning while improving your ability to visualize progress.
In this practical session I’ll cover the basics of user story mapping before walking you through case studies of how our teams are using this approach and the results we are achieving. I'll show you the before, during, and after pictures from several projects so that you can understand how our maps progress during the projects and how we use them to influence iterative development, promote good decision making, and visualize priorities, plans, scope and progress.
This document discusses Alibaba Mobile's ecosystem and strategies for launching products in various markets. It covers Alibaba's entrance into the mobile internet world through smartphones, operating systems, and application stores/browsers. It then discusses how Alibaba builds its ecosystem through big data, content monetization, and various traffic sources. The document outlines Alibaba's strategies for global markets and provides real examples of products launched in India and Indonesia, including services related to cricket, music, video, Facebook notifications, e-commerce, and news.
The Dining Man: how does Afisha Restaurants change the behavioral patterns of choice and payments in cafes and restaurants. Based on the real experience of Project Manager
This document provides a summary of Marvin Liao's 2016 investment outlook. It discusses 7 trends that early stage tech investors should pay attention to:
1. Virtual and augmented reality being the next major engagement platform, as AR/VR startups raised $658M in 2015.
2. The internet of everything (IoT), as IoT startups raised over $1.9B in 2015.
3. FinTech as a major growth area, with Asian FinTech startups raising $3.5B in 2015 and US startups raising $3B in Q1 2015.
4. Millennials now being the largest demographic group and redefining smartphone usage and preferences.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
RxJava is a library for composing asynchronous and event-based programs using observable sequences. It provides features for concurrency, request management, data flow manipulation, and error handling. RxJava uses streams and new objects like Schedulers, Subscriptions, and Subjects. It can be used with techniques like retained fragments, cached observables, binding to lifecycles, and services to handle configuration changes and loading data.
The document discusses the Observer pattern and RxJava. RxJava allows for concurrency, data flow manipulation, and error handling through its use of observables and subscribers. It provides links to documentation on RxJava operators and a blog post that helps explain RxJava fundamentals.
This document discusses Spotify's transition to a "consistent, thin, and dumb" approach to app development. It summarizes Spotify's user and song numbers, the challenges of their previous iOS client, and their shift to a backend-driven model with modular organization. This allows for innovation, scaling, and a unified user experience across platforms through frameworks like GLUE. The document endorses frameworks as "machines" and sharing knowledge and success.
The document summarizes the architectural changes made to the Wunderlist app between versions 2 and 3. Version 3 was completely redesigned with a modular layered architecture that is highly decoupled, enables real-time syncing, and is easier to maintain, test, and adapt compared to the previous monolithic structure. The key layers include presentation, sync, SDK, and model layers with defined boundaries and dependencies between the layers.
The document discusses SoundCloud's approach to mobile testing, including:
- Engineers write unit and UI tests which are run continuously after each code change. Manual testing is also done before releases.
- A test runner service manages test execution across devices in parallel to improve efficiency compared to relying solely on Jenkins.
- An IntelliJ plugin was created to allow testing directly from the IDE for local development, integrating with the test runner service.
The document discusses the VIPER architecture pattern for structuring iOS applications. It begins by introducing the key components of a VIPER module: the View, Presenter, Interactor, Router, and Entity. It then provides examples of how each component is responsible for lifecycle management, event handling, data validation, routing, and other tasks. The document argues that VIPER increases testability, modularity, and code quality of iOS apps. It also promotes open sourcing example VIPER code on GitHub to help disseminate knowledge of this architecture.
MBLTDev15: Anna Mikhina, Maxim Evdokimov, Tinkoff Bank e-Legion
This document discusses working on errors and testing. It focuses on improving performance by identifying mistakes, analyzing what caused them, and learning from the experience to do better in the future. The goal is to enhance skills and knowledge through reflection on past weaknesses or issues uncovered by assessment.
This document discusses Alibaba Mobile's ecosystem and strategies for launching products in various markets. It covers Alibaba's entrance into the mobile internet world through smartphones, operating systems, and application stores/browsers. It then discusses how Alibaba builds its ecosystem through big data, content monetization, and various traffic sources. The document outlines Alibaba's strategies for global markets and provides real examples of products launched in India and Indonesia, including services related to cricket, music, video, Facebook notifications, e-commerce, and news.
The Dining Man: how does Afisha Restaurants change the behavioral patterns of choice and payments in cafes and restaurants. Based on the real experience of Project Manager
This document provides a summary of Marvin Liao's 2016 investment outlook. It discusses 7 trends that early stage tech investors should pay attention to:
1. Virtual and augmented reality being the next major engagement platform, as AR/VR startups raised $658M in 2015.
2. The internet of everything (IoT), as IoT startups raised over $1.9B in 2015.
3. FinTech as a major growth area, with Asian FinTech startups raising $3.5B in 2015 and US startups raising $3B in Q1 2015.
4. Millennials now being the largest demographic group and redefining smartphone usage and preferences.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
RxJava is a library for composing asynchronous and event-based programs using observable sequences. It provides features for concurrency, request management, data flow manipulation, and error handling. RxJava uses streams and new objects like Schedulers, Subscriptions, and Subjects. It can be used with techniques like retained fragments, cached observables, binding to lifecycles, and services to handle configuration changes and loading data.
The document discusses the Observer pattern and RxJava. RxJava allows for concurrency, data flow manipulation, and error handling through its use of observables and subscribers. It provides links to documentation on RxJava operators and a blog post that helps explain RxJava fundamentals.
This document discusses Spotify's transition to a "consistent, thin, and dumb" approach to app development. It summarizes Spotify's user and song numbers, the challenges of their previous iOS client, and their shift to a backend-driven model with modular organization. This allows for innovation, scaling, and a unified user experience across platforms through frameworks like GLUE. The document endorses frameworks as "machines" and sharing knowledge and success.
The document summarizes the architectural changes made to the Wunderlist app between versions 2 and 3. Version 3 was completely redesigned with a modular layered architecture that is highly decoupled, enables real-time syncing, and is easier to maintain, test, and adapt compared to the previous monolithic structure. The key layers include presentation, sync, SDK, and model layers with defined boundaries and dependencies between the layers.
The document discusses SoundCloud's approach to mobile testing, including:
- Engineers write unit and UI tests which are run continuously after each code change. Manual testing is also done before releases.
- A test runner service manages test execution across devices in parallel to improve efficiency compared to relying solely on Jenkins.
- An IntelliJ plugin was created to allow testing directly from the IDE for local development, integrating with the test runner service.
The document discusses the VIPER architecture pattern for structuring iOS applications. It begins by introducing the key components of a VIPER module: the View, Presenter, Interactor, Router, and Entity. It then provides examples of how each component is responsible for lifecycle management, event handling, data validation, routing, and other tasks. The document argues that VIPER increases testability, modularity, and code quality of iOS apps. It also promotes open sourcing example VIPER code on GitHub to help disseminate knowledge of this architecture.
MBLTDev15: Anna Mikhina, Maxim Evdokimov, Tinkoff Bank e-Legion
This document discusses working on errors and testing. It focuses on improving performance by identifying mistakes, analyzing what caused them, and learning from the experience to do better in the future. The goal is to enhance skills and knowledge through reflection on past weaknesses or issues uncovered by assessment.