Keksint旦s辰辰ti旦n Tuotev辰yl辰-ohjelma voi tarjota monenlaista tukea, kun Peloton-konsepteja halutaan vied辰 kohti toteutusta. Tuotev辰yl辰辰 esitteli Mia Fohlin Keksint旦s辰辰ti旦st辰.
Lean kehitt辰misen v辰lineen辰 / MS SOSTE 2016Markus Meurman
油
LEAN on ennen kaikkea tapa ajatella toiminnan kehitt辰mist辰. Toyotan toimintatavoista johdettu ajatusmalli keskittyy erityisesti k辰yt辰nn旦nl辰heiseen jatkuvaan parantamiseen sek辰 ihmisten kunnioittamiseen. N辰en molemmat periaatteet erityisen t辰rkein辰 SOTE-sektorilla, jossa ihminen ja ihmisyys on kaiken keski旦ss辰. LEAN-ty旦kaluja on valtavat m辰辰r辰t, mutta niiden kaikkien k辰ytt辰minen ei ole itsetarkoitus. Ajattelumallin k辰ytt旦旦notto parin hyvin valitun ty旦kalun avulla on erinomainen tapa aloittaa LEAN-kulttuurin rakentaminen.
Kettera hankinta - Miten onnistut kehitysresurssien ostamisessa?Karoliina Luoto
油
Suomessa t辰ll辰 hetkell辰 suosituin ketter辰n hankinnan muoto on resurssien ostaminen. Siin辰 onnistumisen ytimess辰 ovat l辰pin辰kyvyys, vastuu visiosta - my旦s teknologian suhteen, budjetin strateginen k辰ytt辰minen ja kyky yhteisty旦n johtamiseen. Esitys Projektip辰ivill辰 31.10.2017.
Mit辰 lean ohjelmistokehitys on k辰yt辰nn旦ss辰 vuonna 2019? Mit辰 muut voisivat oppia siit辰, miten leani辰 ohjelmistokehitysalalla sovelletaan? Mist辰 pit辰isis aloittaa kun haluaa leaniytt辰辰 softakehityksen? Karoliina Luoto vastasi n辰ihin kysymyksiin Lean 2019 -seminaarissa Scandic Parkissa 26.3.2019.
SAP-ohjelmistojen laadun kehitt辰minen monitoimittajaymp辰rist旦ss辰 - case Elisamikkomr
油
Presentation from the SAP Finug technology seminar (Sep 23-24 2010) highlighting the QM challenges and solutions in a multi vendor environment, Finnish only.
Lean IT katsaus. Lean teollisuustuotannossa, palveluisssa, IT palveluissa, tuotekehityksess辰 ja ohjelmistotuotannossa. Lean IT k辰yt辰nn旦ss辰, Kanban, Scrum, Scrumban.
How to be a Lean Product Developer? @Agile Riga Day 2012Marko Taipale
油
The document provides guidance for lean product development. It recommends:
1. Validating business ideas through customer development and getting feedback to turn ideas into a series of testable hypotheses rather than guesses.
2. Building software faster using techniques like acceptance test-driven development (ATDD) and just-in-time architecture to minimize waste and inventory in the development process.
3. Measuring key metrics to understand customer needs and prioritize features, determine when requirements are met, and track progress over time.
This document describes several case studies involving companies transitioning to more agile ways of working.
The first case study involves an international gaming company that was trying to speed up product development. Mapping their entire value stream and showing areas of waste and delay helped them transition to Scrum and reduce their time-to-market from 24 months to 3 months.
The second case study involves a software product company that was just starting to adopt Scrum. Mapping out their current roles and processes revealed a lack of clear responsibilities that was causing confusion and delays. Introducing a Chief Product Owner role helped clarify responsibilities and align the various teams.
The third case study involves a company that was developing a new way of working to
Let it grow empowering nature in our future cities, Mette SkjoldYIT Corporation
油
Let it grow - Empowering nature in our future cities
Mette Skjold, Managing Director & Partner, Architect, SLA
Urban development puts a massive pressure on the blue and green structures of our natural environment. But why spend resources on suppressing nature in our cities when we can create values for everyday life and prosperity - by setting it free?
Kest辰v辰t kaupunkiymp辰rist旦t seminaari 25.11.2014, Helsinki, Finlandia-talo
Fiksussa Kalasatamassa on nopeiden kokeilujen kautta kiihdytetty kaupunkikehityst辰, avattu mahdollisuus kurkistaa tulevaisuuteen ja osallistettu asukkaita sen luomiseen.
Kokemusten esittelij辰n辰 on Forum Virium Helsingin kehitysp辰辰llikk旦 Katja Spilling. Esitys on pidetty Helsingin kaupungin Digiryhm辰n tapaamisessa 16.11.2016. Katso esityksest辰 videotallenne Helsinki-kanavalta: http://www.helsinkikanava.fi/www/kanava/fi/videot/video?id=3234 .
Luennoin Tampereen teknillisen yliopiston Liiketoimintasuunnitelma kurssilla erilaisista liiketoimintamalleista ja Lean Startup-meneltem辰st辰. T辰ss辰 luentorunkoni tutustuttavaksi.
SAP-ohjelmistojen laadun kehitt辰minen monitoimittajaymp辰rist旦ss辰 - case Elisamikkomr
油
Presentation from the SAP Finug technology seminar (Sep 23-24 2010) highlighting the QM challenges and solutions in a multi vendor environment, Finnish only.
Lean IT katsaus. Lean teollisuustuotannossa, palveluisssa, IT palveluissa, tuotekehityksess辰 ja ohjelmistotuotannossa. Lean IT k辰yt辰nn旦ss辰, Kanban, Scrum, Scrumban.
How to be a Lean Product Developer? @Agile Riga Day 2012Marko Taipale
油
The document provides guidance for lean product development. It recommends:
1. Validating business ideas through customer development and getting feedback to turn ideas into a series of testable hypotheses rather than guesses.
2. Building software faster using techniques like acceptance test-driven development (ATDD) and just-in-time architecture to minimize waste and inventory in the development process.
3. Measuring key metrics to understand customer needs and prioritize features, determine when requirements are met, and track progress over time.
This document describes several case studies involving companies transitioning to more agile ways of working.
The first case study involves an international gaming company that was trying to speed up product development. Mapping their entire value stream and showing areas of waste and delay helped them transition to Scrum and reduce their time-to-market from 24 months to 3 months.
The second case study involves a software product company that was just starting to adopt Scrum. Mapping out their current roles and processes revealed a lack of clear responsibilities that was causing confusion and delays. Introducing a Chief Product Owner role helped clarify responsibilities and align the various teams.
The third case study involves a company that was developing a new way of working to
Let it grow empowering nature in our future cities, Mette SkjoldYIT Corporation
油
Let it grow - Empowering nature in our future cities
Mette Skjold, Managing Director & Partner, Architect, SLA
Urban development puts a massive pressure on the blue and green structures of our natural environment. But why spend resources on suppressing nature in our cities when we can create values for everyday life and prosperity - by setting it free?
Kest辰v辰t kaupunkiymp辰rist旦t seminaari 25.11.2014, Helsinki, Finlandia-talo
Fiksussa Kalasatamassa on nopeiden kokeilujen kautta kiihdytetty kaupunkikehityst辰, avattu mahdollisuus kurkistaa tulevaisuuteen ja osallistettu asukkaita sen luomiseen.
Kokemusten esittelij辰n辰 on Forum Virium Helsingin kehitysp辰辰llikk旦 Katja Spilling. Esitys on pidetty Helsingin kaupungin Digiryhm辰n tapaamisessa 16.11.2016. Katso esityksest辰 videotallenne Helsinki-kanavalta: http://www.helsinkikanava.fi/www/kanava/fi/videot/video?id=3234 .
Luennoin Tampereen teknillisen yliopiston Liiketoimintasuunnitelma kurssilla erilaisista liiketoimintamalleista ja Lean Startup-meneltem辰st辰. T辰ss辰 luentorunkoni tutustuttavaksi.
The document discusses different approaches to agile software development including Scrum, Kanban, Extreme Programming (XP), Lean Startups, and Design Driven Development (D3). It explains that agile is a philosophy focused on individuals, collaboration, adaptability to change, and delivering working software frequently. Specific agile methods then apply this philosophy through practices like test-driven development, daily standups, limiting work in progress, and continuous delivery.
The document discusses several technology trends for 2015, including reactive web development using Meteor, adopting an API-first approach and microservices architecture, implementing continuous delivery practices like releasing software updates almost everyday, using Docker to standardize infrastructure management, and applying lean startup principles like building, measuring, learning, and pivoting products.
Extreme agile leadership - Ans辰tze f端r kooperative F端hrung in einer agilen Or...Jo Seibert
油
In diesem Vortrag m旦chten wir zeigen, welchen Einfluss die Einf端hrung von agiler Softwareentwicklung auf unser F端hrungsverst辰ndnis hatte und welche tiefgreifenden Ver辰nderungen f端r die gesamte Organisation wir daraus gemeinsam entwickelt haben. Insbesondere wollen wir die folgende konkreten Punkte vorstellen:
Von der Pyramide zum Pfirsich: Einfluss des agilen Arbeitens auf die Unternehmensorganisation
Vom geschlossenen Strategiemeeting zum unternehmensweiten Open Space
Von der individuellen Zielvereinbarung zum gemeinsamen Verbesserungsprozess
Vom Vorgesetzten zum Mentorenteam: Dezentralisierung der Personalentwicklung
Vom Zentrum in die Peripherie: Wer entscheidet hier eigentlich?
"Lean startup" is a methodology for launching businesses that emphasizes validated learning, rapid experimentation, and iterative product releases to align offerings with customer needs. It involves creating a Minimum Viable Product (MVP) that allows teams to efficiently test assumptions and gather feedback, ultimately aiming to minimize risk and expedite development. The document also discusses types of pivots in strategy while maintaining a core vision, using examples from various companies to illustrate the lean approach.
The Lean Startup approach, articulated by Eric Ries, applies lean production principles to innovation and emphasizes rapid iterative experimentation, validated learning, and customer feedback. Key concepts include the minimum viable product (MVP), which allows startups to test hypotheses with minimal effort, and innovation accounting to measure progress effectively. The framework promotes understanding customer needs and emphasizes reducing waste while enabling sustainable growth through various models and metrics.
The document summarizes key principles from Eric Ries' book on building successful startups using a "Lean" approach. It discusses 5 principles: (1) entrepreneurs are everywhere, (2) entrepreneurship is management, (3) startups exist to learn how to build a sustainable business through validated learning, (4) the build-measure-learn cycle allows for rapid iteration, and (5) innovation accounting helps prioritize work. It emphasizes the importance of rapid prototyping to validate assumptions and learn quickly from customers through metrics. Pivoting the business model based on learnings, rather than stubbornly sticking to initial ideas, is also highlighted as critical to the Lean approach for building enduring businesses.
The document discusses the principles of the Lean Startup methodology, emphasizing low burn rates, continuous customer interaction, and rapid iterations for product development. It highlights the history of IMVU's founding and their approach to customer discovery and validation, leading to significant revenue growth. The approach encourages agility in response to market changes, allowing startups to adapt quickly and efficiently.
Asiakkuusmarkkinointiliiton ja Kari Korkiakosken tekem辰 white paper k辰sittelee Net Promoter Score -suosittelumallin perusteita ja keinoja hy旦dynt辰辰 sit辰 yrityksen muuttamiseksi asiakasl辰ht旦isemm辰ksi.
Kuvaus: Sitran j辰rjest辰m辰t Vaikuttavuuden Boot Camp -ty旦pajat tukivat yritysten ja j辰rjest旦jen vaikuttavuusl辰ht旦isten palveluiden kehityst辰 vuosina 2018-2019. Kolmen ty旦pajan sarja keskittyi vaikuttavuuden mallintamiseen, vaikutusten mittaamiseen ja vaikuttavuusl辰ht旦isen liiketoiminnan kehitt辰miseen. Koulutuskumppanina toimi Deloitte.
Lisenssi: Attribution-NonCommercial 4.0 International (CC BY-NC 4.0)
Finding a product that people want to buy and useMarko Taipale
油
The document discusses the process of identifying and validating a product idea aimed at helping parents manage sick children, focusing on customer discovery and problem-solving. It emphasizes the importance of understanding customer needs, using a minimum viable product (MVP) to test solutions, and iterating based on feedback. Marko Taipale outlines a model for agile business development, integrating concepts like customer-problem fit, problem-solution fit, and scaling strategies.
Mashing up customers, users, product and businessMarko Taipale
油
The document discusses customer and product development using an agile approach. It emphasizes starting with the customer to identify problems, then developing minimum viable products to validate solutions fit the problems. Each step involves validation, whether validating the customer has a problem, the solution fits the problem, or there is a market for the product. Tools like lean canvases and validation boards help share understanding and co-create. The process is iterative, refining the product based on frequent customer feedback to maximize learning.
How do we use lean startup in service developmentMarko Taipale
油
The document discusses using Lean Startup methodology in service development. It explains that there are three levels of knowing: build-measure-learn. Lean Startup involves developing both the business model and customers through experiments and validation. All projects start with concepts which are developed into business models and hypotheses to be tested. Customer development focuses on problem-solution fit through experiments conducted outside the office with customers. The key is to iterate based on lessons learned from validating assumptions and hypotheses.
Osaaminen uuden yrityksen johtajan n辰k旦kulmastaMarko Taipale
油
Esitys johtamisen osaamisesta. Esitetty 28.5.2013 Johtamisen kehitt辰misverkoston johtoryhm辰n ty旦seminaarissa (Johtamisverkosto ja Sosiaali- ja Terveysministeri旦)
Marko Taipale shares stories from coaching companies through agile adoption challenges. The first story describes helping a subcontractor deliver a project on time by analyzing 600 use cases and improving delivery from 100 to 25 months. The second story addresses misaligned goals between development and sales causing performance issues. The third story shows improving a gaming company's time to market from 24 to 3 months by optimizing the whole product development system rather than just individual teams. Lessons focus on analyzing systems holistically and aligning incentives rather than blaming individuals.
Product Owners, Santa and other GoblinsMarko Taipale
油
The document discusses the role of a product owner (PO) and proposes an alternative approach. It suggests that rather than having a single PO, an organization should take a system-centric view and:
1) Create a customer development team to understand customer value and validate what to build.
2) Connect this team to the development team to understand costs.
3) Ensure the customer development team consists of and meets with stakeholders to understand risks by studying the market and getting feedback from the development team.
4) This approach avoids bottlenecks and allows for more communication and innovation compared to relying only on a single PO role.
From a concept to viable business How do we know if we are building the rig...Marko Taipale
油
This document discusses building the right product by focusing on problem/solution fit, business model/market fit, hypothesis/experiment fit, and user needs/service fit. It emphasizes the importance of validating your concepts by talking to customers and measuring results rather than assuming you know requirements. The key steps outlined are drawing a business model canvas, stating hypotheses to test, and getting customer feedback through discovery and validation. Pivoting based on learnings is important rather than prematurely scaling execution without verifying the business model. Overall the message is to interface business, design and engineering to create successful businesses by making the business the driver.
Maneuver Warfare and Other Badass Habits of a Lean Product DeveloperMarko Taipale
油
This document discusses how to become a lean product developer by adopting habits that focus on efficiency and continuous learning. It recommends "leaning" business ideas through customer validation, building solutions faster or not at all using just-in-time implementation, and continuously measuring what matters to optimize the system and throw away waste. The document emphasizes learning by getting customer feedback, formulating hypotheses to test, using A3 problem solving templates, and shipping solutions frequently to learn from real-world use. The overall message is that respecting people, understanding purpose, improving continuously, and engaging customers are key habits of lean product development.
Provocation to the Product Owner challenge - Agile Coaching CircleMarko Taipale
油
The document discusses challenges with the Product Owner (PO) role in Scrum and Agile processes. It questions whether the single PO model is effective given the amount of information and responsibilities. It also questions what happens between understanding customer needs and generating the product vision and backlog. Additionally, it argues that Agile methods sometimes marginalize understanding the business and customer needs upstream of product development. The document advocates for more learning and direct customer interaction rather than relying solely on the PO as a single point of contact. It poses several questions about how organizations implement the PO role and manage product strategy.
The document describes an Agile consulting and coaching circle that meets monthly for 2.5 hours. Each gathering includes a 20 minute peer coaching session where one person receives feedback, a topic introduction and discussion, and a retrospective and backlog grooming. The circle is meant for sharing and learning in an open group format. Facilitator contact information is provided for questions, ideas or contributions.
Continuous Deployment Nextdoor.fi released every day at Scan-Agile 2011Marko Taipale
油
The document discusses the continuous deployment practices at nextdoor.fi, highlighting daily deployments, automated testing, and efficient bug fixing. With over 550 acceptance tests and minimal operational staff, the process emphasizes real-time monitoring and rapid turnaround. Key lessons include the importance of continuous integration and automated acceptance tests to enhance software delivery and reliability.
The document discusses the principles of a lean startup, emphasizing predictability, adaptability, and continuous deployment. It outlines the methodologies used at nextdoor.fi, detailing their agile development processes, customer engagement, and the importance of validated learning. The author, Marko Taipale, shares insights on improving startup operations through effective team collaboration and iterative development.
Lean Startup for AaltoES Summer of StartupsMarko Taipale
油
The document discusses lean startup principles and how they were applied at Nextdoor.fi. It describes how Nextdoor used short development cycles, frequent releases, customer feedback, and minimum viable products to build their service iteratively while minimizing unused features. They were able to develop and maintain the site with no testers or full-time developers through techniques like continuous delivery, daily backups and reporting, and keeping the product queue small.
The document outlines eight key lessons learned from transitioning to an agile framework, emphasizing the importance of setting goals, committing to agile values, and fostering continuous learning. It highlights the need for businesses to prioritize adaptability and predictability, create and validate product visions with customers, and identify minimum viable products. Additionally, it encourages focusing on optimizing the entire organization and building effective teams to enhance overall agility.
The document is a guide by Marko Taipale on selling Agile methodology to managers, emphasizing the importance of understanding both the product and customer needs for effective value propositions. It outlines a structured process from idea approval to design and deployment, highlighting potential pitfalls. Key quotes from W. Edwards Deming reinforce the importance of methodical approaches in achieving goals.