Project terminology
Site Architecture Terms#
These terms describe product development milestones for HFLA Website 2.0.
Note: some of these milestones have already been reached.
current-projects / home page projects
Refers to the current projects section of the home page. It is also referenced by the “current-projects.html” file.
donor page
To be created is a new donor.html (or similar) file, which is linked and found by clicking the Donor” menu item on the home page (possible “www.hackforla.org/donor.html”). This page will provide information about Hack for LA donors, including level of sponsorship and recognition for contributions made.
projects page
To be created is a new projects.html (or similar) file, which is linked and found by clicking the “Project” menu item on the home page (possibly “www.hackforla.org/projects.html”). This page will display all projects and a filter for finding projects that interest the user.
single project page
To be created is a new project-template.html file (or similar), which provides a deep dive into a single project. This page will have expanded information like team members and links for both the new potential volunteer and the team members.
Software Development Lifecycle Terms#
The below terms describe parts of the software development lifecycle for HFLA Website 2.0.
feature
A product feature is a characteristic of your product that describe its appearance, components, and capabilities. Put another way, it is a slice of business functionality that has a corresponding benefit or set of benefits for that product's end user.
More information: https://www.aha.io/roadmapping/guide/requirements-management/what-are-product-features
user story
A user story is a tool used in Agile software development to capture a description of a software feature from an end-user perspective. It describes the type of user, what they want and why and helps to create a simplified description of a requirement.
More information: https://www.atlassian.com/agile/project-management/user-stories
customer research
Customer research is the process of identifying customer segments, needs, and behaviors. Customer research may be carried out as part of market research, user research, or design research.
More information: https://www.interaction-design.org/literature/topics/customer-research
data requirements
Data requirements, in the context of software development, ensure that the data produced and consumed satisfy organizational objectives, are understood by all relevant stakeholders, and meet the needs of the team that create and use the data.
More information: https://www.healthit.gov/playbook/pddq-framework/data-operations/data-requirements-definition/
acceptance criteria
Acceptance criteria refers to a set of predefined requirements that must be met in order to mark a user story complete. Acceptance criteria are also sometimes called the “definition of done.” They determine the scope and requirements that must be executed by developers to consider a user story finished.
More information: https://www.productplan.com/glossary/acceptance-criteria/ More information: https://rubygarage.org/blog/clear-acceptance-criteria-and-why-its-important
product backlog
A product backlog is a list of new features, changes to existing features, bug fixes, infrastructure changes, or other activities that a team may deliver to achieve a specific outcome. The product backlog is the single authoritative source for things that a team works on.
More information: https://www.agilealliance.org/glossary/backlog/
wireframe
A wireframe is a static, low-fidelity representation of different layouts that form a product. Wireframes communicate structure, content, and functionality of a product, feature, or enhancement.
More information: https://theblog.adobe.com/everything-you-need-to-know-about-wireframes-and-prototypes/
QA
Software QA is the process of ensuring software quality. It often includes tasks like functional testing and source code quality and performance testing.
More information: https://www.mindfulqa.com/qa-sdlc/
usability standards
Usability falls under the broader discipline of user experience and refers to the ease of access and/or use of a product or website. These standards include compliance with ADA standards, which refer to the Americans with Disabilities Act Standards for Accessible Design. These standards state that all electronic and information technology, including websites, must be accessible to people with disabilities.
More information: https://www.interaction-design.org/literature/topics/usability More information: https://www.usability.gov/what-and-why/accessibility.html
product analytics
Product analytics refers to capturing and analyzing quantitative data through embedded tools that record how users interact with a product.
More information: https://mixpanel.com/topics/what-is-product-analytics/
product roadmap
A product roadmap is a shared source of truth that outlines the vision, direction, priorities, and progress of a product over time. It is a plan of action that aligns the team around short- and long-term goals for a product and how they will be achieved.
More information: https://www.atlassian.com/agile/product-management/product-roadmaps
launch
A software launch can be staged into a soft launch before its final release. In a soft launch, a small release is made to a limited group of individuals for beta testing.
More information: https://en.wikipedia.org/wiki/Soft_launch
product management
Product management concerns defining the why, when, and what of a product. A product manager is responsible for setting a product's vision and strategy. A product manager leads cross-functional teams from a product's conception to launch.
More information: https://www.hotjar.com/blog/product-management/
project management
The practice of initiating, planning, executing, controlling, and closing the work of a team to achieve specific goals and meet specific success criteria at the specified time. [3]
More information: https://www.pmi.org/about/learn-about-pmi/what-is-project-management
development
Software development refers to the process of conceiving, specifying, designing, programming, documenting, testing, and bug-fixing to create and maintain applications, frameworks, or other software components.
More information: https://en.wikipedia.org/wiki/Software_development
user interface (UI)/user experience (UX)
User interface (UI) is the series of screens, pages, and visual elements, including buttons, icons, typeface, graphics, and images, that enable a person to interact with a product or service. User experience (UX), on the other hand, is the internal experience a person has as they interact with a product or service.
More information: https://www.usertesting.com/blog/ui-vs-ux
Project management terms#
agile
An iterative approach to project management and software development that helps teams deliver value to their customers faster and with fewer headaches. Instead of betting everything on a "big bang" launch, an agile team delivers work in small, but consumable, increments. [1][2]
kanban
A popular framework used to implement agile software development. Work items are represented visually on a kanban board, allowing team members to see the state of every piece of work at any time. [2]
scrum
A software development framework that describes a set of meetings, tools, and roles that work in concert to help teams structure and manage their work. Scrum encourages teams to learn through experiences, self-organize while working on a problem, and reflect on their wins and losses to continuously improve. [2]
user-centered design
User-centered design (UCD) or user-driven development (UDD) is a framework of processes (not restricted to interfaces or technologies) in which usability goals, user characteristics, environment, tasks and workflow of a product, service or process are given extensive attention at each stage of the design process. [4]
Scrum methodology#
acceptance criteria
Predefined conditions that a software product must satisfy in order to mark a user story complete. [1][2]
epic
A large body of work that can be broken down into a number of smaller user stories. [2]
sprint/iteration
A short period in which the development team implements and delivers a discrete and potentially shippable application increment (e.g. a working milestone version). [2]
user story
Development tasks often expressed as “persona + need + purpose." [2]
velocity
The average amount of work a scrum team completes during a sprint. This can be measured in either "story points" or number of issues. [2]
References#
- Altexsoft blog. https://www.altexsoft.com/blog/. Retrieved 1 December 2019.
- Atlassian Agile Coach. https://www.atlassian.com/agile. Retrieved 1 December 2019.
- Scrum (software development). Wikipedia. https://en.wikipedia.org/wiki/Scrum_(software_development). Retrieved 1 December 2019.
- User-centered design (UCD) or user-driven development (UDD). Wikipedia. https://en.wikipedia.org/wiki/User-centered_design. Retrieved 23 March 2020.