What is involved in User Story Mapping
Find out what the related areas are that User Story Mapping connects with, associates with, correlates with or affects, and which require thought, deliberation, analysis, review and discussion. This unique checklist stands out in a sense that it is not per-se designed to give answers, but to engage the reader and lay out a User Story Mapping thinking-frame.
How far is your company on its User Story Mapping journey?
Take this short survey to gauge your organization’s progress toward User Story Mapping leadership. Learn your strongest and weakest areas, and what you can do now to create a strategy that delivers results.
To address the criteria in this checklist for your organization, extensive selected resources are provided for sources of further research and information.
Start the Checklist
Below you will find a quick checklist designed to help you think about which User Story Mapping related domains to cover and 271 essential critical questions to check off in that domain.
The following domains are covered:
User Story Mapping, Graphical user interface builder, Model-driven development, Software engineering, Requirements analysis, Incremental build model, User experience, Fibonacci scale, Post-it note, Software maintenance, Extreme Programming Practices, Software configuration management, Alistair Cockburn, Software design, UML tools, Agile software development, Integrated development environment, Five Ws, Application release automation, Planning game, User Story Mapping, Domain-driven design, Product Backlog, Kanban board, Software documentation, Acceptance test–driven development, Rapid application development, Pair Programming, Software development, Test-driven development, Stand-up meeting, Software construction, Boundary object, Microsoft Solutions Framework, Waterfall model, Product owner, Software testing, Software development methodology, ISO/IEC JTC 1/SC 7, Continuous Delivery, User story, Feature-driven development, Iterative and incremental development, IEEE Standards Association, Behavior-driven development, Product management, ISO 9001, Extreme Programming, Infrastructure as Code, Build automation, Cleanroom software engineering, Scaled Agile Framework, Software development process, Programming tool, Continuous Integration, Unified Process, Software prototyping, Dynamic systems development method, Software deployment, Software quality assurance, Spiral model, Use case, Team software process:
User Story Mapping Critical Criteria:
Wrangle User Story Mapping results and correct better engagement with User Story Mapping results.
– How do you determine the key elements that affect User Story Mapping workforce satisfaction? how are these elements determined for different workforce groups and segments?
– What management system can we use to leverage the User Story Mapping experience, ideas, and concerns of the people closest to the work to be done?
– What is our User Story Mapping Strategy?
Graphical user interface builder Critical Criteria:
Demonstrate Graphical user interface builder governance and ask what if.
– What role does communication play in the success or failure of a User Story Mapping project?
– What are the usability implications of User Story Mapping actions?
– Is User Story Mapping Required?
Model-driven development Critical Criteria:
Transcribe Model-driven development decisions and be persistent.
– Consider your own User Story Mapping project. what types of organizational problems do you think might be causing or affecting your problem, based on the work done so far?
– Is there a User Story Mapping Communication plan covering who needs to get what information when?
– What knowledge, skills and characteristics mark a good User Story Mapping project manager?
Software engineering Critical Criteria:
Test Software engineering risks and get going.
– DevOps isnt really a product. Its not something you can buy. DevOps is fundamentally about culture and about the quality of your application. And by quality I mean the specific software engineering term of quality, of different quality attributes. What matters to you?
– Record-keeping requirements flow from the records needed as inputs, outputs, controls and for transformation of a User Story Mapping process. ask yourself: are the records needed as inputs to the User Story Mapping process available?
– Can we answer questions like: Was the software process followed and software engineering standards been properly applied?
– Is open source software development faster, better, and cheaper than software engineering?
– What are the business goals User Story Mapping is aiming to achieve?
– Better, and cheaper than software engineering?
– What threat is User Story Mapping addressing?
Requirements analysis Critical Criteria:
Audit Requirements analysis tasks and create a map for yourself.
– Will User Story Mapping have an impact on current business continuity, disaster recovery processes and/or infrastructure?
– What sources do you use to gather information for a User Story Mapping study?
Incremental build model Critical Criteria:
Focus on Incremental build model issues and find the ideas you already have.
– At what point will vulnerability assessments be performed once User Story Mapping is put into production (e.g., ongoing Risk Management after implementation)?
– What are the Key enablers to make this User Story Mapping move?
– What about User Story Mapping Analysis of results?
User experience Critical Criteria:
Accelerate User experience outcomes and find the essential reading for User experience researchers.
– What do you think the world of enterprise software delivery will look like in ten to fifteen years (take into account practices, technology, and user experience)?
– How can I avoid duplication of identity, attributes, and credentials and provide a single sign-on user experience for my users?
– Where does User Experience come from, what does it add to the software development process and what methods are available?
– What prevents me from making the changes I know will make me a more effective User Story Mapping leader?
– What is the difference between information architecture and user experience design?
– What are the potential impacts to user experience by using a cloud-based service?
– What are the problems when integrating Agile Development and User Experience?
– Agile-User Experience Design: With or Without a Usability Expert in the Team?
– What is the difference between customer experience and user experience?
– What are the best-practices for creating a good User Experience?
– How do we go about Comparing User Story Mapping approaches/solutions?
– How would one define User Story Mapping leadership?
– What does User Experience do?
Fibonacci scale Critical Criteria:
Contribute to Fibonacci scale tactics and get answers.
– What are the success criteria that will indicate that User Story Mapping objectives have been met and the benefits delivered?
– How do we go about Securing User Story Mapping?
Post-it note Critical Criteria:
Recall Post-it note tasks and look for lots of ideas.
– Do we cover the five essential competencies-Communication, Collaboration,Innovation, Adaptability, and Leadership that improve an organizations ability to leverage the new User Story Mapping in a volatile global economy?
– To what extent does management recognize User Story Mapping as a tool to increase the results?
– Meeting the challenge: are missed User Story Mapping opportunities costing us money?
Software maintenance Critical Criteria:
Read up on Software maintenance tasks and diversify disclosure of information – dealing with confidential Software maintenance information.
– If the path forward waits until a new generation of devices essentially replaces an old generation of devices which could be somewhere between 5 and 15 years, what does the path forward look like for the legacy devices and their software maintenance?
– How do we Improve User Story Mapping service perception, and satisfaction?
– Are accountability and ownership for User Story Mapping clearly defined?
– What are current User Story Mapping Paradigms?
Extreme Programming Practices Critical Criteria:
Exchange ideas about Extreme Programming Practices tactics and oversee Extreme Programming Practices requirements.
– A compounding model resolution with available relevant data can often provide insight towards a solution methodology; which User Story Mapping models, tools and techniques are necessary?
– What are our needs in relation to User Story Mapping skills, labor, equipment, and markets?
– Are there User Story Mapping Models?
Software configuration management Critical Criteria:
Co-operate on Software configuration management engagements and look at it backwards.
– What tools do you use once you have decided on a User Story Mapping strategy and more importantly how do you choose?
– What potential environmental factors impact the User Story Mapping effort?
– What are some of the software Configuration Management tools?
– Definition: what is software Configuration Management?
– Motivation: why software Configuration Management?
– How will you measure your User Story Mapping effectiveness?
– Why software Configuration Management ?
Alistair Cockburn Critical Criteria:
Deliberate over Alistair Cockburn engagements and remodel and develop an effective Alistair Cockburn strategy.
– Does User Story Mapping analysis show the relationships among important User Story Mapping factors?
– Does User Story Mapping analysis isolate the fundamental causes of problems?
– Have you identified your User Story Mapping key performance indicators?
Software design Critical Criteria:
Have a session on Software design failures and overcome Software design skills and management ineffectiveness.
– Which User Story Mapping goals are the most important?
UML tools Critical Criteria:
Set goals for UML tools engagements and devote time assessing UML tools and its risk.
– What are the top 3 things at the forefront of our User Story Mapping agendas for the next 3 years?
– What are the long-term User Story Mapping goals?
Agile software development Critical Criteria:
Check Agile software development decisions and probe Agile software development strategic alliances.
– The sprint backlog is the list of work the team must address during the next sprint. The list is derived by selecting stories/features from the top of the product backlog until the team feels they have enough work to fill the sprint. Is this done by the team asking, Can we also do this?
– Imagine a scenario where you engage a software group to build a critical software system. Do you think you could provide every last detail the developers need to know right off the bat?
– How can agile software development be utilized when the development is done in several different locations instead of one site?
– Can you afford to lock your business into a rigid long-term project where the cost of change grows exponentially?
– Are meetings viewed as ways for managers to micromanage their teams: what have you done in the last 24 hours?
– What are the best software metrics for discerning Agile (vs. non-Agile) process effects on teams artifacts?
– Do not ISO 9000 and CMM certifications loose their meaning when applied to the software industry?
– What are some keys to successfully conquering ever changing business requirements?
– What other types of systems might be able to benefit from this component?
– Which is really software best practice to us, CMM or agile development?
– Do we know the difference between lean and agile software development?
– What is the best online tool for Agile development using Kanban?
– How Agile are Industrial Software Development Practices?
– What is and why Disciplined Agile Delivery (DAD)?
– How do Web Operators communicate with Developers?
– How could a more enhanced framework be developed?
– Is Internet-speed software development different?
– What are you planning to complete today?
– What makes agile better?
Integrated development environment Critical Criteria:
Derive from Integrated development environment planning and explore and align the progress in Integrated development environment.
– Who is responsible for ensuring appropriate resources (time, people and money) are allocated to User Story Mapping?
– Is the scope of User Story Mapping defined?
Five Ws Critical Criteria:
Reconstruct Five Ws tactics and balance specific methods for improving Five Ws results.
– What is the purpose of User Story Mapping in relation to the mission?
– Are there recognized User Story Mapping problems?
Application release automation Critical Criteria:
Be responsible for Application release automation decisions and overcome Application release automation skills and management ineffectiveness.
– What are the short and long-term User Story Mapping goals?
Planning game Critical Criteria:
Grade Planning game issues and diversify by understanding risks and leveraging Planning game.
– What are your key performance measures or indicators and in-process measures for the control and improvement of your User Story Mapping processes?
– Does User Story Mapping systematically track and analyze outcomes for accountability and quality improvement?
– What are the record-keeping requirements of User Story Mapping activities?
User Story Mapping Critical Criteria:
Dissect User Story Mapping results and catalog User Story Mapping activities.
– How to deal with User Story Mapping Changes?
Domain-driven design Critical Criteria:
Distinguish Domain-driven design planning and reinforce and communicate particularly sensitive Domain-driven design decisions.
– what is the best design framework for User Story Mapping organization now that, in a post industrial-age if the top-down, command and control model is no longer relevant?
Product Backlog Critical Criteria:
Weigh in on Product Backlog results and correct better engagement with Product Backlog results.
– Scrums productivity stems from doing the right things first and doing those things very effectively. The product owner queues up the right work by prioritizing the product backlog. How does the team maximize its productivity, though?
– Do the estimates take into account how long it would take to analyze, design, and code the requirements in the Product Backlog?
– Do User Story Mapping rules make a reasonable demand on a users capabilities?
– Should managers do the estimation of Product Backlog Items?
– What does a Product Backlog look like?
Kanban board Critical Criteria:
Experiment with Kanban board leadership and raise human resource and employment practices for Kanban board.
– Do we all define User Story Mapping in the same way?
– How do we keep improving User Story Mapping?
Software documentation Critical Criteria:
Model after Software documentation strategies and customize techniques for implementing Software documentation controls.
– Do those selected for the User Story Mapping team have a good general understanding of what User Story Mapping is all about?
Acceptance test–driven development Critical Criteria:
Consider Acceptance test–driven development leadership and report on setting up Acceptance test–driven development without losing ground.
– Is Supporting User Story Mapping documentation required?
– How to Secure User Story Mapping?
Rapid application development Critical Criteria:
Value Rapid application development outcomes and get going.
– What type of feasibility is concerned with whether the project violates particular laws or regulations?
– How are we going to realize the benefits of reusability if we keep shrinking the analysis phase?
– Operational feasibility -will the solution fulfill the users requirements?
– Why wait years to develop systems likely to be obsolete upon completion?
– What are the advantages and disadvantages of using a rad proces?
– What is a formalized approach for developing a project schedule?
– Which sdlc results in the highest degree of user participation?
– How do you measure system effectiveness in your organization?
– Technical feasibility -is the solution technically practical?
– Is there a need to exchange data with other applications?
– What are the primary advantages of the traditional sdlc?
– Did usability perceptions change during the rad proces?
– Who are the potential users of the new application?
– How can you tell when a system is successful ?
– How do you decide that a system needs rework?
– Can all end user classes be identified?
– How time-constrained is the project?
– Is the system heavy on computation?
– What is architected rad?
Pair Programming Critical Criteria:
Discuss Pair Programming leadership and describe the risks of Pair Programming sustainability.
– How do we manage User Story Mapping Knowledge Management (KM)?
– What are specific User Story Mapping Rules to follow?
Software development Critical Criteria:
Add value to Software development management and learn.
– As corporate ventures usually go to new business areas and work with new technologies, they are most likely unable to utilize existing commercial or parent corporations in-house development methods. Could Agile Manifesto and agile methods be a good starting point for the corporate venture to start their development effort towards their own, efficient agile in-house software development method?
– Much of the agile advice is oriented towards small teams of up to ten people, who are either co-located or near located, who have ready access to their primary stakeholders, and who are working on software that can be easily organized into a series of small releases. What about large teams?
– What are our metrics to use to measure the performance of a team using agile software development methodology?
– Are there cultural or organizational issues that may affect the system development?
– What if we substitute prototyping for user interface screens on paper?
– Should you have a strict project sequence, or should you be flexible?
– what is the difference between Agile Development and Lean UX?
– WHEN ARE DEFECTS IDENTIFIED IN THE SOFTWARE DEVELOPMENT LIFECYCLE?
– What does software development maturity really mean?
– How Extreme Does Extreme Programming Have to Be?
– What is our Agile methodology?
– Are Agile teams collocated?
– Have we Adopted Agile?
– What is Agility ?
Test-driven development Critical Criteria:
Explore Test-driven development leadership and customize techniques for implementing Test-driven development controls.
– Are there any easy-to-implement alternatives to User Story Mapping? Sometimes other solutions are available that do not require the cost implications of a full-blown project?
Stand-up meeting Critical Criteria:
Drive Stand-up meeting planning and give examples utilizing a core of simple Stand-up meeting skills.
– How do we ensure that implementations of User Story Mapping products are done in a way that ensures safety?
– Stand-up meeting time and format?
Software construction Critical Criteria:
Paraphrase Software construction issues and reduce Software construction costs.
– What are the disruptive User Story Mapping technologies that enable our organization to radically change our business processes?
– How can we incorporate support to ensure safe and effective use of User Story Mapping into the services that we provide?
– Among the User Story Mapping product and service cost to be estimated, which is considered hardest to estimate?
Boundary object Critical Criteria:
X-ray Boundary object risks and learn.
– What new services of functionality will be implemented next with User Story Mapping ?
– Are we Assessing User Story Mapping and Risk?
Microsoft Solutions Framework Critical Criteria:
Think about Microsoft Solutions Framework risks and define what our big hairy audacious Microsoft Solutions Framework goal is.
– Do we aggressively reward and promote the people who have the biggest impact on creating excellent User Story Mapping services/products?
– Do you monitor the effectiveness of your User Story Mapping activities?
Waterfall model Critical Criteria:
Distinguish Waterfall model tasks and look at the big picture.
– Which customers cant participate in our User Story Mapping domain because they lack skills, wealth, or convenient access to existing solutions?
Product owner Critical Criteria:
Derive from Product owner visions and integrate design thinking in Product owner innovation.
– The Product Owner and the Team collaborate to do the best for the business. Each collaboration results in an improved ROI. But how much of an improvement?
– What about when our product is an integration of several different products, each with their own product owner?
– How will we insure seamless interoperability of User Story Mapping moving forward?
– Who fills the Product Owner role?
Software testing Critical Criteria:
Talk about Software testing failures and do something to it.
– Who sets the User Story Mapping standards?
– Why are User Story Mapping skills important?
Software development methodology Critical Criteria:
Prioritize Software development methodology risks and know what your objective is.
– Who are the people involved in developing and implementing User Story Mapping?
– What are our User Story Mapping Processes?
ISO/IEC JTC 1/SC 7 Critical Criteria:
Judge ISO/IEC JTC 1/SC 7 failures and budget the knowledge transfer for any interested in ISO/IEC JTC 1/SC 7.
– Do we have past User Story Mapping Successes?
Continuous Delivery Critical Criteria:
Drive Continuous Delivery planning and observe effective Continuous Delivery.
– A competitive edge, excellent. Focus on continuous delivery. Move on to continuous deployment because that is going to provide your business value. But look at your individual business. Look at your environment and say is that what gives us the competitive edge?
– Does your organization run a Continuous Integration and Continuous Delivery (CI/CD) process?
– What are the barriers to increased User Story Mapping production?
– What is our formula for success in User Story Mapping ?
– Does your organization hope to achieve continuous delivery?
User story Critical Criteria:
Guard User story issues and overcome User story skills and management ineffectiveness.
– How can you negotiate User Story Mapping successfully with a stubborn boss, an irate client, or a deceitful coworker?
– What happens to the function of the business analysis in user story development?
– Have the types of risks that may impact User Story Mapping been identified and analyzed?
Feature-driven development Critical Criteria:
Audit Feature-driven development results and know what your objective is.
– Will User Story Mapping deliverables need to be tested and, if so, by whom?
Iterative and incremental development Critical Criteria:
Reason over Iterative and incremental development outcomes and look at it backwards.
– How does the organization define, manage, and improve its User Story Mapping processes?
IEEE Standards Association Critical Criteria:
Participate in IEEE Standards Association strategies and get answers.
Behavior-driven development Critical Criteria:
Reason over Behavior-driven development adoptions and define what do we need to start doing with Behavior-driven development.
– How do we measure improved User Story Mapping service perception, and satisfaction?
– What vendors make products that address the User Story Mapping needs?
Product management Critical Criteria:
Recall Product management decisions and do something to it.
– A vital question in new product management is: how should the business most effectively invest its research and development (r&d) and new product resources?
– In marketplace businesses what is the optimal relationship between product management Category Management and marketing?
– What is the optimal relationship between Product Management Category Management and Marketing?
– Is the User Story Mapping organization completing tasks effectively and efficiently?
– What are the a best practices for Agile SCRUM Product Management?
– How much does User Story Mapping help?
ISO 9001 Critical Criteria:
Deliberate over ISO 9001 projects and handle a jump-start course to ISO 9001.
– Think about the functions involved in your User Story Mapping project. what processes flow from these functions?
– Does a supplier having an ISO 9001 or AS9100 certification automatically satisfy this requirement?
– Can Management personnel recognize the monetary benefit of User Story Mapping?
Extreme Programming Critical Criteria:
Exchange ideas about Extreme Programming tactics and correct better engagement with Extreme Programming results.
– In the case of a User Story Mapping project, the criteria for the audit derive from implementation objectives. an audit of a User Story Mapping project involves assessing whether the recommendations outlined for implementation have been met. in other words, can we track that any User Story Mapping project is implemented as planned, and is it working?
– Do we monitor the User Story Mapping decisions made and fine tune them as they evolve?
– When using Extreme Programming?
– What Is Extreme Programming?
Infrastructure as Code Critical Criteria:
Be responsible for Infrastructure as Code projects and maintain Infrastructure as Code for success.
– How do we Lead with User Story Mapping in Mind?
Build automation Critical Criteria:
Reconstruct Build automation governance and reinforce and communicate particularly sensitive Build automation decisions.
– How will you know that the User Story Mapping project has been successful?
Cleanroom software engineering Critical Criteria:
Accumulate Cleanroom software engineering goals and drive action.
Scaled Agile Framework Critical Criteria:
Ventilate your thoughts about Scaled Agile Framework issues and probe using an integrated framework to make sure Scaled Agile Framework is getting what it needs.
– How do we make it meaningful in connecting User Story Mapping with what users do day-to-day?
Software development process Critical Criteria:
Contribute to Software development process risks and document what potential Software development process megatrends could make our business model obsolete.
– What will drive User Story Mapping change?
– What is Effective User Story Mapping?
Programming tool Critical Criteria:
Wrangle Programming tool risks and develop and take control of the Programming tool initiative.
– Think about the people you identified for your User Story Mapping project and the project responsibilities you would assign to them. what kind of training do you think they would need to perform these responsibilities effectively?
Continuous Integration Critical Criteria:
Powwow over Continuous Integration goals and observe effective Continuous Integration.
– How do you incorporate cycle time, productivity, cost control, and other efficiency and effectiveness factors into these User Story Mapping processes?
– Can we do User Story Mapping without complex (expensive) analysis?
– Will we use Continuous Integration?
Unified Process Critical Criteria:
Depict Unified Process projects and devise Unified Process key steps.
– What are our best practices for minimizing User Story Mapping project risk, while demonstrating incremental value and quick wins throughout the User Story Mapping project lifecycle?
– Who is the main stakeholder, with ultimate responsibility for driving User Story Mapping forward?
Software prototyping Critical Criteria:
Dissect Software prototyping governance and budget the knowledge transfer for any interested in Software prototyping.
Dynamic systems development method Critical Criteria:
Merge Dynamic systems development method issues and display thorough understanding of the Dynamic systems development method process.
Software deployment Critical Criteria:
Transcribe Software deployment planning and secure Software deployment creativity.
Software quality assurance Critical Criteria:
Analyze Software quality assurance results and define Software quality assurance competency-based leadership.
– Does the software Quality Assurance function have a management reporting channel separate from the software development project management?
– Are software Quality Assurance tests a part of the general hardware acceptance test on the customers machine before it leaves the factory?
– Do software Quality Assurance test programs undergo the same production cycle and method (except q/a) as the software they test?
– Is software Quality Assurance done by an independently reporting agency representing the interests of the eventual user?
– Who will be responsible for making the decisions to include or exclude requested changes once User Story Mapping is underway?
– Is at least one person engaged in software Quality Assurance for every ten engaged in its fabrication?
– What are the best practices for software quality assurance when using agile development methodologies?
– In a project to restructure User Story Mapping outcomes, which stakeholders would you involve?
– Why should we adopt a User Story Mapping framework?
Spiral model Critical Criteria:
Deduce Spiral model quality and know what your objective is.
– Where do ideas that reach policy makers and planners as proposals for User Story Mapping strengthening and reform actually originate?
Use case Critical Criteria:
Unify Use case risks and devise Use case key steps.
– Are responsibilities clear across monitoring market developments, engagement, internal communication, driving use cases?
– What tools specific functionality do clients use the most often in data management to what degree and for what use case?
– Are NoSQL databases used primarily for applications or are they used in Business Intelligence use cases as well?
– Are there select partners in your peer group that may allow you to share thinking and build use cases together?
– Are there select use cases you want to incubate and lead for your organization or business?
– Of the different industry use cases, what are the top ones that you want to monitor?
– How can the internet of things represent an innovative use case in our sector?
– What are the use cases that your org is targeting currently for its CMDB/CMS?
– Are there potential use cases that your organization wants to drive?
– How can the best Big Data solution be chosen based on use case requirements?
– What killer use cases in mobile payments have not been considered?
– What are the best use cases for Mobile Business Intelligence?
– Are any competitors experimenting with use cases?
– Do we have Things use cases?
Team software process Critical Criteria:
Audit Team software process quality and diversify by understanding risks and leveraging Team software process.
– Risk factors: what are the characteristics of User Story Mapping that make it risky?
This quick readiness checklist is a selected resource to help you move forward. Learn more about how to achieve comprehensive insights with the User Story Mapping Self Assessment:
Author: Gerard Blokdijk
CEO at The Art of Service | theartofservice.com
Gerard is the CEO at The Art of Service. He has been providing information technology insights, talks, tools and products to organizations in a wide range of industries for over 25 years. Gerard is a widely recognized and respected information expert. Gerard founded The Art of Service consulting business in 2000. Gerard has authored numerous published books to date.
To address the criteria in this checklist, these selected resources are provided for sources of further research and information:
User Story Mapping External links:
StoriesOnBoard – The User Story Mapping Tool
User Story Mapping with Jeff Patton – YouTube
User story mapping – DiUS
Graphical user interface builder External links:
graphical user interface builder_pdf – docscrewbanks.com
GRAPHICAL USER INTERFACE BUILDER GNUSTEP
GUIB – Graphical User Interface Builder
Model-driven development External links:
Model-Driven Development with IBM Rational Rhapsody – YouTube
Model-Driven Development | Eclipse Converge 2017
Model-Driven Development of .NET Enterprise Applications
Software engineering External links:
Home – enjoy.ing | We enjoy software engineering!
Software Engineering – UTS Faculty of Engineering and IT
RICO: User Experience Design and Software Engineering
Requirements analysis External links:
Dynamic maintenance requirements analysis in asset management
Requirements Analysis Document (RAD) – Brandeis University
Data Requirements Analysis Process – knowledge
Incremental build model External links:
Essays.se: INCREMENTAL BUILD MODEL
Incremental Build model | COMPLEX TESTER
Incremental build model by John Brock on Prezi
User experience External links:
Appico – User experience and interface design studio
Ikara Group – Take control of user experience
User experience (UX) research, design, and consulting | ResIM
Post-it note External links:
Post-It Note Pads – R U OK? Merchandise
Post-It Note – Inventors Art Fry and Spencer Silver
Post-It Note Holder: 5-Minute Gifts! – YouTube
Software maintenance External links:
Timetabling – Software Maintenance (SMA)
Software Maintenance Agreement | Exclaimer
Software Maintenance Agreement (SMA) | simPRO Australia
Extreme Programming Practices External links:
Extreme Programming practices for your team – YouTube
Software configuration management External links:
Software Configuration Management Meetups – Meetup
Set up the software configuration management environment
SCMWise Software Configuration Management – Home | Facebook
Alistair Cockburn External links:
Alistair Cockburn (@TotherAlistair) | Twitter
Software design External links:
WebVolta Web Application Software Design and Developement
Software Design Document (SDD) Template
Division-M | Advanced Software Design
UML tools External links:
Resources – UML tools for software development and Modelling
UML Tools News – Home | Facebook
Agile software development External links:
AOE: Agile Software Development & Technology Provider | AOE
Agile Software Development Company | Techifide
What is Agile Software Development? | Agile Alliance
Integrated development environment External links:
tIDE (Tilemap Integrated Development Environment) – Home
Quick Tour of the Integrated Development Environment
Flowhub | Integrated Development Environment
Five Ws External links:
The Five Ws and an H | Brand Identity Basics | Treehouse
News Stories and the Five Ws – English Worksheets Land
Five Ws Chart (Benjamin Franklin) What happened?
Application release automation External links:
Application Release Automation | Automic Software
MyST 5.5: Application Release Automation for Oracle Middleware
Application Release Automation with Database Automation
Planning game External links:
Changing the urban planning game – GWI
The Great Planning Game by Roberto Rocco – issuu
Planning game play claim | Business News
User Story Mapping External links:
StoriesOnBoard – The User Story Mapping Tool
Silver Stories Features | User Story Mapping
User Story Mapping ebook by Jeff Patton – Rakuten Kobo
Domain-driven design External links:
Domain-Driven Design Europe 2018
Domain-Driven Design | Archfirst
Overview and Core Values of Domain-Driven Design – Part One
Product Backlog External links:
Timebox – Agile Product Backlog Estimation and Planning
Product Backlog Item (Scrum) – msdn.microsoft.com
Kanban board External links:
Kanban Boards | Kanbanize Kanban Board Software
How to Create a Kanban Board | Smartsheet
Kanban Board – How to Make and Use Kanban Boards
Software documentation External links:
Welcome! – Customer Support Software Documentation – 1
Frequently Asked Questions [Oxwall Software Documentation]
Software documentation – RMIT University
Rapid application development External links:
Rapid Application Development with Glade 3.0 part 1 – YouTube
Rapid Application Development (RAD) | LANSA
Elevate Web Builder – Rapid Application Development
Pair Programming External links:
Pair Programming – YouTube
Pair Programming Benefits: The Business Rationale
Remote Pair Programming (San Francisco, CA) | Meetup
Software development External links:
Enterprise Software Development | delegate group
Software Development Company | Synotive
Quantum Software Solutions – Custom Software Development
Test-driven development External links:
The Pros and Cons of Test-Driven Development | Lean Testing
Guidelines for Test-Driven Development
Test-Driven Development: Extensive Tutorial – Leanpub
Stand-up meeting External links:
Daily Ritual: The Stand-Up Meeting – EMG
Scania has a stand-up meeting on the shopfloor – Konftel
Is Your Stand-Up Meeting Getting Boring? – LAUNCH!
Software construction External links:
Software Construction and Design 2 – The University of Sydney
COMP041 – Software Construction 17s2 Course Goals
COMP041 Software Construction
Boundary object External links:
Boundary Object – Home | Facebook
Part I: What is a Boundary Object?
The digital music boundary object – University of Wollongong
Microsoft Solutions Framework External links:
Microsoft Solutions Framework (MSF) Overview
Waterfall model External links:
Waterfall Model in SDLC by Assignment Help – issuu
How is V-Model different from Waterfall model? – Quora
The Waterfall Model – YouTube
Product owner External links:
Sample Test: SAFe® 4 Product Owner/Product Manager
Course: Professional Scrum Product Owner – Elabor8
Product Owner – Scaled Agile Framework
Software testing External links:
ISTQB – Software Testing Training Courses | ILX Group USA
HUSTEF | Hungarian Software Testing Forum
Vansah ™ Software Testing, QA & Monitoring | TestPoint
Software development methodology External links:
Custom Software Development Methodology – Blueberry
Software development methodology by Brand 4u – issuu
Agile Software Development Methodology Tips Tricks – YouTube
ISO/IEC JTC 1/SC 7 External links:
US TAG to ISO/IEC JTC 1/SC 7, Software and Systems Engineering
IEC – ISO/IEC JTC 1/SC 7 Dashboard > Scope
Continuous Delivery External links:
GoCD – Open Source Continuous Delivery and Automation Server
Continuous Delivery (CD) – Trunk Based Development
Principles – Continuous Delivery
User story External links:
User Story Mapping with Jeff Patton – YouTube
How to Run a User Story Workshop – Payton Consulting
User Story Mapping – O’Reilly Media
Feature-driven development External links:
Overview: Agile Essence: Feature-Driven Development
Feature-Driven Development by tosh liang on Prezi
An Introduction to Feature-Driven Development – DZone Agile
Iterative and incremental development External links:
Iterative and incremental development – Usage (kb)
Iterative and Incremental Development (RAD) – SlideShare
Iterative and Incremental development – Kids.Net.Au
IEEE Standards Association External links:
IEEE Standards Association – YouTube
IEEE Standards Association – IEEE 1349 Working Group
IEEE Standards Association – Sign In
Behavior-driven development External links:
Behavior-Driven Development vs. Testing | James Bach’s Blog
Behavior-Driven Development: The Origins | Tricentis
Behavior-Driven Development: The Origins – DZone Agile
Product management External links:
An Agile Product Management Software | leanGears
MAPI Product Management Forum
Folding Burritos – Practical Product Management
ISO 9001 External links:
GMP Labeling, GMP and ISO 9001 Compliance made easier
ISO 9001 Certification, Accreditation, Audit
ISO 9001/ISO 14001/ISO 27001 Online Training | Advisera
Extreme Programming External links:
Scrum, Scrumban and Extreme Programming | Intland Software
What is Extreme Programming? Webopedia Definition
Extreme Programming Values
Infrastructure as Code External links:
Infrastructure as Code – YouTube
What is Infrastructure as Code? | DevOps – Visual Studio
Terraform: Infrastructure as code – Part I – The Practical Dev
Build automation External links:
Software Build Automation with Jenkins – YouTube
Best Build Automation Software in 2017 | G2 Crowd
Cleanroom software engineering External links:
CLEANROOM SOFTWARE ENGINEERING – YouTube
Scaled Agile Framework External links:
Implementation Roadmap – Scaled Agile Framework
SAFe® Scaled Agile Framework | codeBeamer ALM
Scaled Agile Framework (SAFe) Certified Training
Software development process External links:
Technical Software Development Process in the XML Domain
Software Development Process – CodeTee
Basic Steps of Software Development Process – issuu.com
Programming tool External links:
2N® Lift1 Programming Tool – 2N
Description of the programming tool Peter – Gemtree Software
NUMICRO ISP PROGRAMMING TOOL FOR GX2/4 – SMOK® …
Continuous Integration External links:
Continuous Integration (CI) – Gartner IT Glossary
Continuous Integration & Automated Software Builds
Continuous integration – Freehackers
Unified Process External links:
Rational Unified Process – YouTube
Standards, compliance, and Rational Unified Process – IBM
What is Rational Unified Process (RUP)? Webopedia Definition
Software prototyping External links:
Software Prototyping – INGSOFTWARE
Software Prototyping Services. Prototype Development
Software Prototyping Company – Home | Facebook
Dynamic systems development method External links:
Dynamic Systems Development Method – YouTube
DSDM: Dynamic Systems Development Method | Flow Less
Software deployment External links:
On-Premise Software Deployment | Agiloft Hybrid SaaS
About Software Deployment in Essentials
Ultimate Software Deployment Checklist & Deployment Plan
Software quality assurance External links:
Introduction to software quality assurance – YouTube
100% Software Quality assurance company – TESTTailor
Software Quality Assurance – onTy Toom’s Professional Site
Spiral model External links:
Methodology-Spiral Model Essay Example for Free
Spiral Model In Software Engineering in hindi – YouTube
HSM: a hierarchical spiral model for knowledge management
Use case External links:
Baby Monitor with Camera Use Case | Nanny Cam | Arlo
ECM Benefits by Business Application or Use Case | M-Files
Use Case Diagram – YouTube
Team software process External links:
Tema 3. TSP (Team Software Process) – YouTube
Introduction to the Team Software Process | StickyMinds
Team Software Process (PSP/TSP) | JCSE