The Framework for Agile Living Labs (FALL) projects aim to provide practitioners with actionable guidelines on how to run a Living Lab project in an agile way. Developed by imec.livinglabs
Agility and planning : tools and processesJérôme Kehrli
In this presentation, I intend to present the fundamentals, the roles, the processes, the rituals and the values that I believe a team would need to embrace to achieve success down the line in Agile Software Development Management - Product Management, Team Management and Project Management - with the ultimate goal of making planning and forecasting as simple and efficient as it can be.
Refactoring for Software Design Smells - 1 day Workshop Ganesh Samarthyam
Fred Brooks in his book "The Mythical Man Month" describes how the inherent properties of software make its design an "essential" difficulty. Good design practices are fundamental requisites to address this difficulty. One such good design practice is identifying and addressing 'smells'. Most practitioners know about identifying and refactoring code smells. However, there is a lack of awareness on refactoring design smells and architecture smells, which are also equally important for creating high quality software. This presentation provides an in-depth coverage of design smells and how you can refactor them (with most examples from JDK 7.0).
Agility and planning : tools and processesJérôme Kehrli
In this presentation, I intend to present the fundamentals, the roles, the processes, the rituals and the values that I believe a team would need to embrace to achieve success down the line in Agile Software Development Management - Product Management, Team Management and Project Management - with the ultimate goal of making planning and forecasting as simple and efficient as it can be.
Refactoring for Software Design Smells - 1 day Workshop Ganesh Samarthyam
Fred Brooks in his book "The Mythical Man Month" describes how the inherent properties of software make its design an "essential" difficulty. Good design practices are fundamental requisites to address this difficulty. One such good design practice is identifying and addressing 'smells'. Most practitioners know about identifying and refactoring code smells. However, there is a lack of awareness on refactoring design smells and architecture smells, which are also equally important for creating high quality software. This presentation provides an in-depth coverage of design smells and how you can refactor them (with most examples from JDK 7.0).
This is the slide deck for my talk at Global Knowledge on 14 May 2010 for Malaysia VS ALM User Group. I was sharing about the new Agile Process Template that is based on Scrum.
Discussion Post 1A software process model is a streamlined port.docxmadlynplamondon
Discussion Post 1:
A software process model is a streamlined portrayal of a product procedure. Each model speaks to a procedure from a particular point of view. The straightforward reason for these methods is to offer an altered programming advancement according to the prerequisites. Now and then they are otherwise called software improvement life cycle (SDLC) approaches. There are different sorts of models:
1. Waterfall model: When we have an organized procedure and when our necessities are clear as in basic frameworks that need itemized, exact, and precise archives to portray the framework to be delivered. It isn't acceptable when prerequisites are not satisfactory and on the off chance that they continually change and not defenseless for client communication. The periods of the cascade model are: Requirements, Design, Implementation, Testing, and Maintenance.
2. Prototype model: This model is utilized for the advancement of an early example, or the arrival of an item worked to test an idea. This is helpful when prerequisites aren't clear. In spite of the fact that it needs great apparatuses, brisk turn of events, and significant expenses. The periods of a model are: Establish goals, Define model usefulness, Develop the model, Evaluate the model.
3. Incremental and Iterative: They are appropriate for huge tasks and are more affordable to the difference in prerequisites since they bolster client associations with every addition. They don't fit into little ventures or very much organized tasks. The periods of iterative advancement are Inception, Elaboration, Construction, Transition.
4. Spiral: It is useful for highly hazardous or enormous ventures where the necessities are questionable. The venture's prosperity is exceptionally reliant on the hazard examination stage. It doesn't function admirably for littler ventures. Each circle in the winding speaks to a stage. Each circle is part of four areas: Objective setting, Risk appraisal, and decrease, Development, and approval, Planning.
5. Agile: It suits little medium size undertaking, with quick changes in the necessities as a client is included during each stage. Exceptionally constrained arranging is required to begin with the undertaking. There are a few distinctive dexterous techniques accessible, for example, Scrum, Crystal, Agile Modeling (AM), Extreme Programming (XP), and so on.
Discussion Post -2
Rapid Prototyping Model
It follows an iterative model of software development. This model is certainly found to be focusing on implementing the simple and initial phase but finds it difficult and complex when setting the broader feature when it is completed. Reduction of cost and time wastage along with improvement of model user-friendliness serves as its major strengths while inadequate analysis and high cost of prototype implementation give its limitation (Scacchi, W. 2002).
Advantages:
- Absolutely unacceptable for ...
The presentation is guide for the New Project managers and Scrum Masters .It has been prepared considering the basics of Projects and Project Management upto the fine detailing of the Scrum Agile Framework.
Ofcourse the contents are the guiding material and not exhaustive in nature.The contents shall help the Scrum Masters & Project Managers to have deep understanding for the Scrum Framework and adopt in day to day practise in order to successfully deliver the project within the given constrains
5th Annual Forum of the EU Strategy for the Adriatic and Ionian Region. The virtual forum under the slogan “Strengthening the resilience of the Adriatic and Ionian Region through cooperation” took place on 28 - 29 January 2021. It was jointly organized by the Republic of Serbia, the European Commission and with the support of the EUSAIR Facility Point.
This is the slide deck for my talk at Global Knowledge on 14 May 2010 for Malaysia VS ALM User Group. I was sharing about the new Agile Process Template that is based on Scrum.
Discussion Post 1A software process model is a streamlined port.docxmadlynplamondon
Discussion Post 1:
A software process model is a streamlined portrayal of a product procedure. Each model speaks to a procedure from a particular point of view. The straightforward reason for these methods is to offer an altered programming advancement according to the prerequisites. Now and then they are otherwise called software improvement life cycle (SDLC) approaches. There are different sorts of models:
1. Waterfall model: When we have an organized procedure and when our necessities are clear as in basic frameworks that need itemized, exact, and precise archives to portray the framework to be delivered. It isn't acceptable when prerequisites are not satisfactory and on the off chance that they continually change and not defenseless for client communication. The periods of the cascade model are: Requirements, Design, Implementation, Testing, and Maintenance.
2. Prototype model: This model is utilized for the advancement of an early example, or the arrival of an item worked to test an idea. This is helpful when prerequisites aren't clear. In spite of the fact that it needs great apparatuses, brisk turn of events, and significant expenses. The periods of a model are: Establish goals, Define model usefulness, Develop the model, Evaluate the model.
3. Incremental and Iterative: They are appropriate for huge tasks and are more affordable to the difference in prerequisites since they bolster client associations with every addition. They don't fit into little ventures or very much organized tasks. The periods of iterative advancement are Inception, Elaboration, Construction, Transition.
4. Spiral: It is useful for highly hazardous or enormous ventures where the necessities are questionable. The venture's prosperity is exceptionally reliant on the hazard examination stage. It doesn't function admirably for littler ventures. Each circle in the winding speaks to a stage. Each circle is part of four areas: Objective setting, Risk appraisal, and decrease, Development, and approval, Planning.
5. Agile: It suits little medium size undertaking, with quick changes in the necessities as a client is included during each stage. Exceptionally constrained arranging is required to begin with the undertaking. There are a few distinctive dexterous techniques accessible, for example, Scrum, Crystal, Agile Modeling (AM), Extreme Programming (XP), and so on.
Discussion Post -2
Rapid Prototyping Model
It follows an iterative model of software development. This model is certainly found to be focusing on implementing the simple and initial phase but finds it difficult and complex when setting the broader feature when it is completed. Reduction of cost and time wastage along with improvement of model user-friendliness serves as its major strengths while inadequate analysis and high cost of prototype implementation give its limitation (Scacchi, W. 2002).
Advantages:
- Absolutely unacceptable for ...
The presentation is guide for the New Project managers and Scrum Masters .It has been prepared considering the basics of Projects and Project Management upto the fine detailing of the Scrum Agile Framework.
Ofcourse the contents are the guiding material and not exhaustive in nature.The contents shall help the Scrum Masters & Project Managers to have deep understanding for the Scrum Framework and adopt in day to day practise in order to successfully deliver the project within the given constrains
5th Annual Forum of the EU Strategy for the Adriatic and Ionian Region. The virtual forum under the slogan “Strengthening the resilience of the Adriatic and Ionian Region through cooperation” took place on 28 - 29 January 2021. It was jointly organized by the Republic of Serbia, the European Commission and with the support of the EUSAIR Facility Point.
Presentations by:
Dario Marmo and Laura Martelloni. LAMA Agency. Firenze. Italy.
José Francisco Pelaez Peña. LABe Digital Gastronomy Lab. San Sebastián - Donostia. Basque Country. Spain.
Ariana Nastaseanu and Emanuela Flora. European Agency for SMEs -EASME-. European Commission. Europe.
Chair: Fernando Vilariño (ENoLL, CVC, Library Living Lab)
Narend Baijnath. Council on Higher Education, South Africa
Maria-Theresa Norn. Think Tank DEA, Denmark
Esteban Romero Frías. Medialab, University of Granada, Spain
Marko Teräs. Tampere University of Applied Sciences (TAMK), Finland
Presented cases:
Jose María Romero. The response of the Galician Health Living Lab ecosystem to COVID- 19. Galician
Health Living Lab (Galicia, Spain)
Giuseppe Fico. The EiT Health Living Labs: reaction and beyond the COVID- 19 crisis. EiT Health Living
Labs (International Institution)
Amy Wilson. Insights gained from Australia on the COVID19- pandemic. Global Centre for Modern
Aging (Tonsley, Australia)
MODERATOR: Fernando Vilariño (ENoLL Chairperson, Library Living Lab)
Bruce Hsu, Kay Chen. Citizens and mobility in the control of the pandemic. Taiwan Living Lab. Taiwan.
Artur Serra. CatSud: A proposal for a Colaboratori for a regional network of social innovation. i2Cat, Catalonia, Spain.
Kaisa Spilling. Mission Zero Foodprint: Solutions in the context of COVID-19. Forum Virium Helsinki, Finland.
Raúl Oliván, Laia Sánchez. The initaitive frenalacurva.net. (International Project)
Rosa Paradell, Miquel Angel Pérez and Pat González. Hackovid: The people’s hackathon: Confronting the Confinement. i2Cat, Catalonia, Spain.
Presenters:
Jordi Reynés, Clara Borràs, Martí Burriel: The infrastructure of city’s maker spaces to the service of the maker community in Barcelona, Catalonia. (Spain).
Elisenda Casanelles: Building up respirators for COVID-19, from Leitat, Barcelona, Catalonia. (Spain)
Wim de Kinderen: Engaging the 3D printing infrastructures and stakeholders in Eindhoven (Netherlands).
Juan Bertolín: Maker community and University’s Living Lab University engagement in Castelló, Comunitat Valenciana. (Spain).
Moderator: Fernando Vilariño
Jordi Reynés, Clara Borràs, Martí Burriel: The infrastructure of citie’s maker spaces to the service of the maker community in Barcelona, Catalonia. (Spain).
Elisenda Casanelles: Building up respirators for COVID-19, from Leitat, Barcelona, Catalonia. (Spain)
Wim de Kinderen: Engaging the 3D printing infrastructures and stakeholders in Eindhoven (Netherlands).
Juan Bertolín: Maker community and University’s Living Lab University engagement in Castelló, Comunitat Valenciana. (Spain).
ENoLL Director Zsuzsanna Bodi spoke about ENoLL's work with Sustainable Development Goals and how the implementation of SDGs is accelerated by working collaboratively. G-STIC inspired ENoLL to position its 2018 edition of the annual event OpenLivingLab Days around the Sustainable Development Goals.
More from European Network of Living Labs (ENoLL) (20)
Salma Karina Hayat is Conscious Digital Transformation Leader at Kudos | Empowering SMEs via CRM & Digital Automation | Award-Winning Entrepreneur & Philanthropist | Education & Homelessness Advocate
Best Crypto Marketing Ideas to Lead Your Project to SuccessIntelisync
In this comprehensive slideshow presentation, we delve into the intricacies of crypto marketing, offering invaluable insights and strategies to propel your project to success in the dynamic cryptocurrency landscape. From understanding market trends to building a robust brand identity, engaging with influencers, and analyzing performance metrics, we cover all aspects essential for effective marketing in the crypto space.
Also Intelisync, our cutting-edge service designed to streamline and optimize your marketing efforts, leveraging data-driven insights and innovative strategies to drive growth and visibility for your project.
With a data-driven approach, transparent communication, and a commitment to excellence, InteliSync is your trusted partner for driving meaningful impact in the fast-paced world of Web3. Contact us today to learn more and embark on a journey to crypto marketing mastery!
Ready to elevate your Web3 project to new heights? Contact InteliSync now and unleash the full potential of your crypto venture!
When listening about building new Ventures, Marketplaces ideas are something very frequent. On this session we will discuss reasons why you should stay away from it :P , by sharing real stories and misconceptions around them. If you still insist to go for it however, you will at least get an idea of the important and critical strategies to optimize for success like Product, Business Development & Marketing, Operations :)
Reflect Festival Limassol May 2024.
Michael Economou is an Entrepreneur, with Business & Technology foundations and a passion for Innovation. He is working with his team to launch a new venture – Exyde, an AI powered booking platform for Activities & Experiences, aspiring to revolutionize the way we travel and experience the world. Michael has extensive entrepreneurial experience as the co-founder of Ideas2life, AtYourService as well as Foody, an online delivery platform and one of the most prominent ventures in Cyprus’ digital landscape, acquired by Delivery Hero group in 2019. This journey & experience marks a vast expertise in building and scaling marketplaces, enhancing everyday life through technology and making meaningful impact on local communities, which is what Michael and his team are pursuing doing once more with Exyde www.goExyde.com
What You're Going to Learn
- How These 4 Leaks Force You To Work Longer And Harder in order to grow your income… improve just one of these and the impact could be life changing.
- How to SHUT DOWN the revolving door of Income Stagnation… you know, where new sales come into your magazine while at the same time existing sponsors exit.
- How to transform your magazine business by fixing the 4 “DON’Ts”...
#1 LEADS Don’t Book
#2 PROSPECTS Don’t Show
#3 PROSPECTS Don’t Buy
#4 CLIENTS Don’t Stay
- How to identify which leak to fix first so you get the biggest bang for your income.
- Get actionable strategies you can use right away to improve your bookings, sales and retention.
Explore Sarasota Collection's exquisite and long-lasting dining table sets and chairs in Sarasota. Elevate your dining experience with our high-quality collection!
Textile Chemical Brochure - Tradeasia (1).pdfjeffmilton96
Explore Tradeasia’s brochure for eco-friendly textile chemicals. Enhance your textile production with high-quality, sustainable solutions for superior fabric quality.
How to Build a Diversified Investment Portfolio.pdfTrims Creators
Building a diversified investment portfolio is a fundamental strategy to manage risk and optimize returns. For both novice and experienced investors, diversification offers a pathway to a more stable and resilient financial future. Here’s an in-depth guide on how to create and maintain a well-diversified investment portfolio.
How to Build a Diversified Investment Portfolio.pdf
Framework for Agile Living Labs - FALL
1. FRAMEWORK FOR AGILE LIVING LABS
WHY?
FALL
FALL V2 IN 9 STEPS
The Living Lab concept proposes a number of guidelines (user-centric design, iterative in-the-wild testing, user involvement & panel
management, etc…), yet does not offer much in term of practical guidance on how to run an innovation project in real-life. Agile project
management methodologies do offer such guidance yet have been critiqued for not providing a focus on the end-user. The Framework for Agile
Living Labs (FALL) projects aim to provide practitioners with actionable guidelines on how to run a Living Lab project in an agile way. Agility
means being able to flexibly integrate new information in the project’s roadmap, which is exactly the type of situation that a Living Lab project
will find itself in, due to its focus on iterative testing with end-users.
author: imec application prototyping and living labs
A first version of FALL has been described in http://www.timreview.ca/article/1048. Since then, imec’s Application prototyping and Living Lab
(APLL) department have refined its application in numerous projects. This has been revised into FALL v2, based on our most recent experiences.
The method is particularly focused on practitioners and its aim is to provide actionable insights on how to perform Living Lab projects in an
agile way.
Various agile project management methods exist. FALL is based on SCRUM, which takes an approach that is composed of steps that are limited in
time (i.e. timeboxed) and focusses on incremental delivery. SCRUM structures communications in a project, making sure that expectations are
managed correctly and that the team discusses critical issues. You can read more on SCRUM on https://en.wikipedia.org/wiki/
Scrum_(software_development).
Framework for
Agile
Living Labs
2 To map & validate the assumptions that are being made, organiZe an Innovatrix workshop
The innovatrix is a process-structuring innovation management framework. It makes explicit the current knowledge on which the innovation is
based and identifies key knowledge deficits in the form of assumptions that need to be tested.
Based on extensive experience with Living Lab-projects, the framework was built on the following eight innovation-relevant criteria:
Customer Segment, Needs, Current Practices, Value Proposition, Solution, Barriers, Value Capture and Key Partners.
At the start of an innovation project, during a kick-off workshop, each of the criteria of the framework is 'filled' with relevant input from the
innovator. This input is initially gathered through probing questions in which the facilitator of the innovatrix workshop plays an important role.
This input is then awarded one of the following statuses, based on the nature and strength of the input:
- Assumption (the input is assumed)
- Validated (the input is validated by research)
- Invalidated (the input is invalidated by research)
- New insights and unknown (no input is given).
Depending on the assumption status, the input is mapped on different-coloured post-its: yellow (assumptions), green (validated assumption),
red (invalidated) and blue (new insights).
In the initial Innovatrix kick-off workshop innovation-related assumptions are mapped, key uncertainties are identified and focus for future
research activities are set. In follow-up sessions, the initial assumptions are, in dialogue with the entrepreneur,– updated by changing its status.
This innovation management framework is being developed in a digital tool to better – and systematically – use this approach in Living Lab
Projects
4 Transfer the stories to a backlog
The output of the user story workshop is a list of prioritized user stories that can be added to the project backlog. This will structure the work
that needs to be done. For collecting these user stories, agile development tools can be used, like Atlassian’s Jira (https://www.atlassian.com/
blog/agile/how-to-manage-a-product-backlog-with-ease), which imec’s APLL department uses.
Other tools similar to Jira (VersionOne, PivotalTracker, Workzone, Targetprocess, etc) allow user stories to be listed in the backlog and to manage
the stories that have been committed in each sprint. A sprint is a period of time during which project work is done. These tools make sure that
the teamwork can be tracked. This can for example be done by indicating for each story that it is "in progress" or "done".
6 Quantify the user stories in the backlog using story points
Typically, a sprint will be 2 to 3 weeks. To be able to estimate the effort that is needed for a certain sprint, it is important to quantify the
amount of work that needs to be completeed through planning poker
Here’s how to do it: planning poker is a process in which the various members of a team indicate how much effort it will take to perform each
user story. This results in essential to the team communication on the nature of the work and allows the work to be planned more accurately.
https://en.wikipedia.org/wiki/Planning_poker
5 Draft the architecture
An information system requires a number of building blocks to play together in order to allow the functionalities of the system to be realized.
This is why an architecture is needed, so the development team know what to build and how to connect the various building block together. In
larger projects where different teams work on different building blocks, the architecture will offer guidance on who does what.
For example, an architecture could have a graphical presentation, indicating that a system will have a database that will store data and that will
be processed by a server. This server would perform machine learning algorithms and would send out data so that end-users can consult that
data through an iOS or an Android smartphone app.
7 Iteratively define and perform sprints
At the beginning of each sprint, a number of backlog items are selected and are assigned to the members of the team. At the end of the sprint,
the idea is that a prototype should be delivered that can be tested
9 End of the project
If all the objectives of the project have been met or time or budget have run out, the project should break out of the iterative loop and end the
project.
The deliverable of the FALL process as a whole can be either a prototype or a product. A prototype is created purely to learn, like when one is
doing academic research or when it is important to first find out how a solution would look before going to market. A product is a full-fledged
system that can be brought to market. It is important to note that, when the objective is to do academic research, the learnings from building
the prototype should be abstracted to contribute to literature in the domain to which the prototype belongs.
8 At the end of each sprint, test the results as much as possible with end users
This produces valuable insights on the purpose of the system and its usability. Do the end-users feel that the system is one which they find
valuable? Do they feel that the system is easy to use? User Researchers and User Involvement Coordinators are essential in setting up and
collecting the feedback from users. It is essential that Product Owners pay attention to user feedback and make changes to the backlog to
reflect new insights.
After the test phase, the iterative process can start again Transfer the user stories to the backlog (step 4). The test phase will have yielded new
insights, which will add new needed functionality (and therefore will introduce new stories in the backlog), make planned functionality obsolete,
or changed the priority of planned functionality.
Sprint n Sprint n+1 Sprint n+2
3 To get a clear view on what a system should do, organize a story mapping workshop
The story mapping workshop should be lead by the Product Owner, or a User Researcher (as described above). It assists the Product Owner in
collecting data that represents the needs of end-users and stakeholders. A user story workshop has the following phases:
• Organization: Introduce the workshop’s structure
• Introduction: The idea that underlies the system: what is the general objective that the
system aims to reach?
• User story generation: Each participant is asked to write down user stories on post-it
notes. A user story has the following structure: “as a <actor>, I want to <objective> in
order to <motivation>”. For example: As an <email user>, I want to be able to <flag an
email> in order to <remember that I need to follow it up later on>.
• User story presentation and grouping: Each workshop participant presents the user
stories that she came up with and posts them on a wall. User stories that in some way
belong together are clustered on the wall and are given a group name. These group
names are referred to as “epics” in Scrum.
• Assinging value: When all post-its have been posted, the person who leads the
workshop goes over each of the user stories with the other participants and writes one
of the following categories on it: must have, should have, could have and won’t have.
This is a very important part of the workshop, as feature creep almost always occurs.
Feature creep refers to the fact that people have the tendency to assign functionality to
a system that does not provide much value. It is therefore essential for the project to
focus first on the user stories that deliver the most value.
• Prioritization and strategic release of user stories: Through the prioritization of the
user stories, different releases can be planned of the system, focusing first on the high-
impact user stories.
1 Set roles
Process Manager
The Process Manager understands the method
well and guides the team in how to apply the
process of FALL, similar to a SCRUM master in
the SCRUM methodology.
Product Owner
The Product Owner has the responsibility of
keeping the story backlog up to date from the
perspective of the end users and the
stakeholders. As such, they represents the
stakeholders and makes sure that the project
meets their needs. The Product Owner
preferably has the skills to understand the
needs of end-users, rather than a pure
technical skill set.
Researcher
Researchers take the lead in getting input from
users at different stages of the project.
Architect
Architects create the systems architecture,
update and prioritize the backlog in terms of
the stories that are not facing towards the user,
such as “the server backend should be able to
automatically backup the user data that is
stored in the database”.
UX Designer
User Experiene (UX) designers are responsible
for creating designs that represent the GUI
(graphical user interface) of the system. These
can be wireframes, clickable prototypes, or GUI
mock-ups. It is crucial to note that, although
the UX designer holds the skillset to build
these artifacts, creating them should never be
done solely from the perspective of the UX
designer. Core to the philosophy of FALL is that
the UX designer should work with the feedback
that was gathered from the project actors
(other team members, representative end users,
etc.).
Developer
The Developer is responsible for translating the
story back- log into functional applications.
User INVOLVEMENT & Panel Management
As users don't automatically find their way to
one of the FALL projects, a User Involvement
Coordinator is a crucial role. They put the 'user'
in 'user research', pave the way for users to
participate in FALL projects, and make
sure participants stay motivated throughout
the project.
User
Users are involved in the project to bring
domain oriented knowledge to the team
through co-design and usability testing
processes. They are guided by the user
researcher. It is important that the users
involved in FALL projects be as representative
as possible of the user group that will
eventually use the outcome of the project.
Stakeholder
Like users, Stakeholders are also involved in
contributing domain-oriented knowledge. They
are not necessarily representative of the
eventual user population, however Stakeholders
often hold higher-level interest than users and
operate from a policy, commercial, or academic
point of view.
www.imec.be
4. Maintain8. Test
6. Quantify7. Plan
3. Map user stories
5. Draft architecture
2. Map & validate assumptions
through Innovatrix
1. Set roles