Enterprise Architecture Quarter

Product Design Quarter (hereinafter, the Quarter) is the third of four lectures of Project Quadrivium (hereinafter, the Quadrivium):

• The Quarter is designed to introduce its learners to enterprise design, or, in other words, to concepts related to creating architecture for achieving enterprise goals; and
• The Quadrivium examines concepts of administering various types of enterprises known as enterprise administration as a whole.

The Quadrivium is the first of seven modules of Septem Artes Administrativi, which is a course designed to introduce its learners to general concepts in business administration, management, and organizational behavior.

Lecture outline

The predecessor lecture is Business Analysis Quarter.

Concepts

1. Product vision statement. A brief statement or paragraph that describes the why, what, and who of the desired software product from a business point of view.
   • Product vision statement. a high-level description of a product which includes who it is for, why it is necessary and what differentiates it from similar products.
   • Product. A solution or component of a solution that is the result of a project.
   • Feature. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each feature is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.
   • Defect. A deficiency in a product or service that reduces its quality or varies from a desired attribute, state, or functionality. See also requirements defect.
2. Product backlog. A set of user stories, requirements or features that have been identified as candidates for potential implementation, prioritized, and estimated.
   • Backlog. A changing list of product requirements based on the customer’s needs. The backlog is not a to-do list; rather, it is a list of all the desired features for the product. The Agile team uses the backlog to prioritize features and understand which features to implement first.
   • Backlog grooming. The process that occurs at the end of a sprint, when the team meets to make sure the backlog is ready for the next sprint. The team may remove user stories that aren’t relevant, create new stories, reassess priority, or split user stories into smaller tasks. Backlog grooming is both an ongoing process and the name for the meeting where this action occurs (a backlog grooming meeting).
   • Product backlog item (PBI). A single element of work that exists in the product backlog. PBIs can include user stories, epics, specifications, bugs, or change requirements. The product owner of an Agile team compiles and prioritizes the product backlog, putting the most urgent or important PBIs at the top. PBIs comprise tasks that need to be completed during a Scrum sprint—a PBI must be a small enough increment of work to be completed during a single sprint. As PBIs move up to a higher priority in the product backlog, they are broken down into user stories.
   • Product backlog. The list of requirements requested by the customer. The product backlog is not a to-do list; rather, it is a list of all the features the customer has requested be included in the project. The requirements include both functional and non-functional customer requirements, as well as technical team-generated requirements. While there are multiple inputs to the product backlog, it is the sole responsibility of the product owner to prioritize the product backlog. During a Sprint planning meeting, backlog items are moved from the product backlog into a sprint, based on the product owner's priorities.
   • Sprint backlog. A segment of Product Backlog Items (PBIs) that the team selects to complete during a Scrum sprint. These PBIs are typically user stories taken from the product backlog.
3. Acceptance criteria. Specification for a set of conditions that the product must meet in order to satisfy the customer. In Agile development, the product owner writes statements from the customer’s point of view that explain how a user story or feature should work. In order for the story or feature to be accepted it needs to pass the acceptance criteria; otherwise, it fails.
   • Acceptance test. The derivative from the acceptance criteria that verifies whether a feature is functional. The test has only two results: pass or fail. Acceptance criteria usually include one or more acceptance tests.
4. Branding. The process of creating and marketing a consistent idea or image of a product, so that it is recognizable by the public.
5. Product life cycle.
   • Lifecycle. Important phases in the development of a system from initial concept through design, testing, use, maintenance, to retirement.

• Interaction model. A design model that binds an application together in a way that supports the conceptual models of its target users. It defines how all of the objects and actions that are part of an application interrelate, in ways that mirror and support real-life user interactions.
• Service design. The practice of designing a product according to the needs of users, so that the service is user-friendly, competitive and relevant to the users.
• Service. Work carried out or on behalf of others.
• Visual design. Also called communication design. A discipline which combines design and information development in order to develop and communicate a media message to a target audience.
• Wireframe. A rough guide for the layout of a website or app, either done with pen and paper or with wireframing software.
• Action design. A change process based on systematic collection of data and then selection of a change action based on what the analyzed data indicate.
• Commitment concept. Plans should extend for enough to meet those commitments made when the plans were developed.
• Load chart. A modified Gantt chart that schedules capacity by entire departments or specific resources.
• Organizational development. A collection of planned change interventions, built on humanistic-democratic values, that seeks to improve organizational effectiveness and employee well-being.
• Organizational development. Change methods that focus on people and the nature and quality of interpersonal work relationships.
• Statement of work (SOW). A narrative description of products or services to be supplied under contract.

1. • Statement of work (SOW). A formal document that defines the entire scope of the work that shall be completed in order to implement the proposed change.

Roles

1. Agile team. A work team that is responsible for committing to work, delivering and driving the product forward from a tactical perspective in terms of Agile development. Usually, an Agile team is a small, high-functioning group of five to nine people who collaboratively work together to complete an iteration or project. The team has the necessary skills and competencies to work on the project. Scrum teams are cross-functional; Kanban teams can either be cross-functional or specialists. Scrum teams lack any roles. Kanban teams usually have team leads.
   • Agile team member. A member of an Agile team. Often, Agile team include engineers, architects, developers, analysts, QA experts, testers, UX designers, etc.
   • Team lead.
2. Scrum role. One of the following: product owner, Scrum master, Agile team member.
   • Scrum master. A facilitator for the team and product owner. Rather than manage the team, the Scrum master works to assist both the team and product owner in the following ways: (1) Remove the barriers between the development and the product owner so that the product owner directly drives development. (2) Teach the product owner how to maximize return on investment (ROI), and meet his/her objectives through Scrum. (3) Improve the lives of the development team by facilitating creativity and empowerment. (4) Improve the productivity of the development team in any way possible. (5) Improve the engineering practices and tools so that each increment of functionality is potentially shippable. (6) Keep information about the team's progress up to date and visible to all parties. Scrum master is often viewed as the coach for the team.
   • Product owner. A person who holds the vision for the product and is responsible for maintaining, prioritizing and updating the product backlog. In Agile development, the product owner has final authority representing the customer's interest in backlog prioritization and requirements questions. This person must be available to the team at any time, but especially during the Sprint planning meeting and the Sprint review meeting. Challenges of being a product owner: (1) Resisting the temptation to "manage" the team. The team may not self-organize in the way you would expect it to. This is especially challenging if some team members request your intervention with issues the team should sort out for itself. (2) Resisting the temptation to add more important work after a Sprint is already in progress. (3) Being willing to make hard choices during the sprint planning meeting. (4) Balancing the interests of competing stakeholders.
3. Customer. The organization or individual that has requested (and will pay for) a product or service.
4. Project sponsor.

• Regulator. A stakeholder with legal or governance authority over the solution or the process used to develop it.
• Stakeholder. An individual or group affected in some way by the undertaking. Stakeholders are valuable sources for requirements.
• Stakeholder. Anyone outside the Scrum team who has an interest in the product that the team is producing. Stakeholders can include but are not limited to direct managers, subject matter experts, account managers, salespeople, and legal officers.

Methods

1. Development methodology.
   • Methodology. A set of processes, rules, templates, and working methods that prescribe how business analysis, solution development and implementation is performed in a particular context.
   • Plan-driven methodology. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Plan-driven methodologies emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.
   • Change-driven methodology. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.
2. Agile development. The project management approach of developing increments of software in frequent iterations based on evolving requirements. The Agile Manifesto was the initial public declaration for Agile development related to software. Its authors believed that they found "better ways of developing software by doing it and helping others do it."
   • Agile software development methodology. A methodology fundamentally incorporating iteration and continuous feedback to refine and deliver a software system. It involves continuous planning, testing, integration, and other forms of continuous evolution of both the project and the software.
   • Scrum. The most widely used framework under the Agile umbrella. Scrum is an iterative software model that follows a set of predefined roles, responsibilities, and meetings. In Scrum, iterations are called sprints and are assigned a fixed length—sprints typically last one to two weeks, but can last as long a month.
   • Lean Agile development. An example of lightweight Agile methodology applied to project development. Lean Software Development combines the Lean manufacturing approach pioneered by Toyota in the 1950s (also known as just-in-time production) and Lean IT principles, and applies them to software. LSD places a strong emphasis on people and effective communication. LSD is defined by seven principles: (1) Eliminate waste, (2) Create knowledge, (3) Build quality in, (4) Defer commitment, (5) Optimize the whole, (6) Deliver fast, (7) Respect people
   • Lean UX. Inspired by Lean and Agile development theories, Lean UX speeds up the UX process by putting less emphasis on deliverables and greater focus on the actual experience being designed.
   • Test-driven development (TDD). The practice of designing and building tests for functional, working code, and then building code that will pass those tests.
3. Kanban. A highly visual framework that falls under the Agile umbrella. The Kanban process uses continuous work flow rather than fixed iterations to produce shippable deliverables. When applied over an existing process, Kanban encourages small, incremental changes to the current process and does not require a specific set up or procedure. Kanban focuses on completing entire projects rather than sprints.
4. Iterative design. A methodology based on a cyclic process of prototyping, testing, analysing, and refining a product or process. Based on the results of testing the most recent iteration of a design, changes are made. This process is intended to ultimately improve the quality and functionality of a design.
   • Iterate. The act of repeating a process with the aim of approaching a desired goal, target or result. Each repetition of the process is also called an iteration.
   • Iteration. A fixed or timeboxed period of time, generally spanning two to four weeks, during which an Agile team develops a deliverable, potentially shippable product. A typical Agile project consists of a series of iterations, along with a Sprint planning meeting prior to development and a Sprint retrospective at the end of the iteration. Iterations are referred to as sprints in Scrum.
   • Iterative development. The process of breaking down projects into more manageable components known as iterations. Iterations are essential in Agile methodologies for producing a potentially shippable deliverable or product.
5. Waterfall model. A sequential design process where progress is seen as flowing steadily downwards through the phases of Conception > Initiation > Analysis > Design > Construction > Testing > Implementation > Maintenance.

Instruments

1. Scrum meeting. One of the following: story time, Sprint planning meeting, Sprint review meeting, Sprint retrospective, daily standup.
   • Sprint planning meeting. A working session held before the start of each sprint to reach a mutual consensus between the product owner's acceptance criteria and the amount of work the development team can realistically accomplish by the end of the sprint. The length of the sprint determines the length of the Sprint planning meeting, with two hours being equivalent to one week of the sprint. Using this formula, the Sprint planning meeting for a two-week sprint would last about four hours, although this can vary.
   • Daily standup. A brief communication and status-check session facilitated by the Scrum Master where Scrum teams share progress, report impediments, and make commitments for the current iteration or sprint. The Daily Scrum consists of a tightly focused conversation kept to a strict timeframe; the meeting is held at the same time, every day (ideally, in the morning), and in the same location. The Scrum task board serves as the focal point of the meeting. During the Daily scrum each team member answers three questions: (1) "What have I done since the last Scrum meeting? (i.e. yesterday)" (2) "What will I do before the next Scrum meeting? (i.e. today)" (3) "What prevents me from performing my work as efficiently as possible?"
   • Story time. A regular work session where items on the backlog are discussed, refined and estimated and the backlog is trimmed and prioritized.
   • Scrum of scrums. A meeting that is a scaling mechanism used to manage large projects involving Scrum multiple teams. A Scrum of Scrums is held to facilitate communication between teams that may have dependencies on one another. One member from each team attends the Scrum of Scrums to speak for the team—this could be the Scrum Master but may be any team member who can effectively relay information and handle questions or concerns for the team.
   • Sprint review meeting. A meeting that a Scrum team holds immediately following the completion of a sprint to review and demonstrate what the team has accomplished during the sprint. This meeting is attended by the product owner or customer, Scrum Master, Scrum team, and stakeholders. The Sprint review meeting is an informal meeting (no Powerpoint slides allowed). The length of the sprint determines the length of the Sprint review meeting, with one hour being equivalent to one week of the sprint. Using this formula, the Sprint planning meeting for a two-week sprint would last two hours, although this can vary.

Results

1. Product scope. The features and functions that characterize a product, service or result.
   • Scope. The area covered by a particular activity or topic of interest. See also project scope and solution scope.
   • Scope model. A model that defines the boundaries of a business domain or solution.

Practices

• Capability. A function of an organization that enables it to achieve a business goal or objective.
• Capacity. The amount of work that can be completed within a certain time frame and is based on the number of hours that an individual or team will be available to complete the work.
• Collaborative design. Inviting input from users, stakeholders and other project members.
• Decomposition. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
• Diary Study. Asking users to record their experiences and thoughts about a product or task in a journal over a set period of time.
• Domain. The problem area undergoing analysis.
• Evaluation. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time, and to identify ways to improve the solution to better meet objectives. See also metric, indicator and monitoring.
• Impact analysis. An impact analysis assesses the effects that a proposed change will have on a stakeholder or stakeholder group, project, or system.
• Initiative. Any effort undertaken with a defined goal or objective.
• Mood Board. A collage, either physical or digital, which is intended to communicate the visual style a direction is heading.
• Objective. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
• Object-oriented modeling. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one another. In some organizations, the same approach is used for business engineering to describe and package the logical components of the business.
• Operational support. A stakeholder who helps to keep the solution functioning, either by providing support to end users (trainers, help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).
• Operative rule(s). The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions, prevent people from taking actions, or prescribe the conditions under which an action may be taken.
• Optimization. The process of choosing the best alternative that will satisfy the needs of the stakeholders under the constraints given (e.g. cost, schedule and available technology).
• Organizational process asset. All materials used by groups within an organization to define, tailor, implement, and maintain their processes.
• Organizational readiness assessment. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
• Pair programming. A scenario where two programmers share a single workstation and work together to develop a single feature.
• Prioritization. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
• Problem statement. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
• Progressive disclosure. An interactive design technique that helps maintain the focus of a user’s attention by reducing clutter, confusion, and cognitive workload. It improves usability by presenting only the minimum data required for the task at hand. The principle is also used in journalism’s ‘inverted pyramid’ style, learning’s ‘spiral approach’, and the game ‘twenty questions’.
• Sitemap. A complete list of all the pages available on a website.
• Spike. A short, time-boxed piece of research, usually technical, on a single story that is intended to provide just enough information that the team can estimate the size of the story
• Stakeholder analysis. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
• Stakeholder Interviews. Conversations with the key contacts in the client organization funding, selling, or driving the product.
• Stakeholder list, roles, and responsibility designation. A listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.
• Structural rule. Structural rules determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
• Sustainable pace. The pace that an Agile team can work at indefinitely without resulting in developer burnout (ideally 40 hours per week).
• Swarming. Mutual work of team members with appropriate skills work together to complete a task that a team member is having trouble completing on his or her own.
• Swimlane. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
• Technical debt. refers to the obligation a development team incurs when they use a short-term, expedient approach to developing a software package without considering the long-term consequences. Technical debt increases project cost and complexity due to inefficiencies, inaccuracies, and other issues introduced into the software package. Poor management, incompetency, timeline pressure, or inadvertent mistakes can all contribute to technical debt.
• Technique. Techniques alter the way a business analysis task is performed or describe a specific form the output of a task may take.
• Trade-off. losing one quality or aspect of something in return for gaining another quality or aspect.
• Unit testing. A short program fragment written for testing and verifying a piece of code once it is completed. A piece of code either passes or fails the unit test. The unit test (or a group of tests, known as a test suite) is the first level of testing a software development product.
• User feedback loop. Ideas are put in front of users, who provide their feedback, which is used to refine the design, and then the process repeats.
• User journey. The step by step journey that a user takes to reach their goal.
• User research. Observation techniques, task analysis, and other feedback methodologies which are used to focus on understanding user behaviors, needs, and motivations.
• Value. The benefit enjoyed by the stakeholders of the system when the system is in operation.

The successor lecture is Project Management Quarter.