Explore chapters and articles related to this topic
Agile project management and lean
Published in John M. Nicholas, Herman Steyn, Project Management for Engineering, Business and Technology, 2020
John M. Nicholas, Herman Steyn
Scrum substitutes all-at-once, upfront definition at a single time with step-wise definition spread over multiple sprints. Customer needs and wants as listed in the product backlog are minimally defined—initially in the form of “user stories” or “epics,” and are refined and expanded over time. Since the desired functions/features and other details of the product are initially unknown, it is more practical to define the product in terms of stories than specific requirements. Each story is a simple statement from the user’s perspective about a product’s potential use, benefits, functionality, or capability, typically written on a 3 × 5 card or sticky note and in the format “As a <type of user>, I want <some goal> because <some reason>.” The focus of each sprint is to satisfy a few user stories. A user story that has multiple goals and is too large to be addressed in one sprint is called an epic. Epics must eventually be broken down into simpler user stories that can each be handled in a sprint.
Project Scope Management
Published in J. Kent Crawford, Project Management Maturity Model, 2021
Epics are containers for initiatives of significant size to fulfill a strategic business objective that create most of the value for the organization. They are aligned with the strategic vision and strategic objectives of the organization and are of sufficient investment size that they require a business case such as the Epic Brief and budgetary endorsement before execution. Epics are typically 3–9 months in duration and are owned by the Product Manager.
Archiving System for EAST PF Power Supply
Published in Fusion Science and Technology, 2022
Guanghong Wang, Shiying He, Ge Gao, Peng Fu, Zejing Wang, Xiaojiao Chen, Xiuqing Zhang, Ying Zuo, Lingpeng Li, Liansheng Huang
The monitor system of the Experimental Advanced Superconducting Tokamak (EAST) poloidal field (PF) power supply1 runs on Linux operation, based on the Experimental Physics and Industrial Control System (EPICS), and uses Control System Studio (CSS) as the human-machine interface. EPICS is an open source control system toolkit used in hundreds of large and small experimental physics projects, and there are many standard tools to use, reducing the code written of the interface and ensuring a unified standard interface.2,3 CSS includes some plugins, such as alarm handler and archive engine.4,5 Archive engine is developed for data archiving. In this paper, the data are collected by the EPICS input/output controller (IOC) via channel access (CA), and the engine places data in the relational database (RDB), which can be browsed through CSS.
The Design and Implementation of the Remote Control and Visualization System for Pulse Application Experiments
Published in Fusion Science and Technology, 2022
Yu Gu, Mengqi Fan, Tengfei Cao, Yuanzhe Zhao, Xiaodan Zhang
This is the reason why we redesigned the system architecture using the Experimental Physics and Industrial Control System4 (EPICS), which is based on the idea of decentralization. EPICS enables all parts of the system to become modular and reflects integration in the overall architecture rather than in one certain point of the system, thus making the overall system load balanced. The design of the remote control and visualization system (RCVS) is also derived from this idea. With the continuous development of computer technology, especially of computer network technology, the rise of the mobile office makes the traditional personal computer–based client-side operating platform not the only option for pulse experimenters to manage pulse experiments.