The Experts below are selected from a list of 42 Experts worldwide ranked by ideXlab platform
Diane M. Strong - One of the best experts on this subject based on the ideXlab platform.
-
The Effect of Task and Tool Experience on Maintenance CASE Tool Usage
Advances in Information Resources Management, 2020Co-Authors: Mark T. Dishaw, Diane M. StrongAbstract:Computer-Aided Software Engineering (CASE) tools have been advocated for improving maintainer productivity and the quality of maintained software. While there is evidence that such benefits can accrue to organizations adopting maintenance-oriented CASE tools, a key problem in achieving the desired benefits from CASE tools is low usage of these tools by programmers. The previously tested Maintenance Tool Utilization Model was a first step in investigating the factors that affect whether maintainers choose to use CASE tools during maintenance Projects. We test the addition of experience with software maintenance tools and with the software maintenance task to the Maintenance Tool Utilization Model. The role of experience is important because managers can provide training to increase experience and they can ensure that Project teams have some members experienced with the tools or with the task. Data for the test are collected from software maintainers working on their organization’s normal maintenance Project Backlog. Tool experience is significant as both a main and interaction effect, but task experience adds little to the explanatory power of the Maintenance Tool Utilization Model. These results support the value of improved CASE tool training programs.
-
The Effect of Task and Tool Experience on Maintenance CASE Tool Usage
Information Resources Management Journal, 2003Co-Authors: Mark T. Dishaw, Diane M. StrongAbstract:Computer-aided software engineering CASE tools have been advocated for improving maintainer productivity and the quality of maintained software. While there is evidence that such benefits can accrue to organizations adopting maintenance-oriented CASE tools, a key problem in achieving the desired benefits from CASE tools is low usage of these tools by programmers. The previously tested Maintenance Tool Utilization Model was a first step in investigating the factors that affect whether maintainers choose to use CASE tools during maintenance Projects. We test the addition of experience with software maintenance tools and with the software maintenance task to the Maintenance Tool Utilization Model. The role of experience is important because managers can provide training to increase experience and they can ensure that Project teams have some members experienced with the tools or with the task. Data for the test are collected from software maintainers working on their organization's normal maintenance Project Backlog. Tool experience is significant as both a main and interaction effect, but task experience adds little to the explanatory power of the Maintenance Tool Utilization Model. These results support the value of improved CASE tool training programs.
Mark T. Dishaw - One of the best experts on this subject based on the ideXlab platform.
-
The Effect of Task and Tool Experience on Maintenance CASE Tool Usage
Advances in Information Resources Management, 2020Co-Authors: Mark T. Dishaw, Diane M. StrongAbstract:Computer-Aided Software Engineering (CASE) tools have been advocated for improving maintainer productivity and the quality of maintained software. While there is evidence that such benefits can accrue to organizations adopting maintenance-oriented CASE tools, a key problem in achieving the desired benefits from CASE tools is low usage of these tools by programmers. The previously tested Maintenance Tool Utilization Model was a first step in investigating the factors that affect whether maintainers choose to use CASE tools during maintenance Projects. We test the addition of experience with software maintenance tools and with the software maintenance task to the Maintenance Tool Utilization Model. The role of experience is important because managers can provide training to increase experience and they can ensure that Project teams have some members experienced with the tools or with the task. Data for the test are collected from software maintainers working on their organization’s normal maintenance Project Backlog. Tool experience is significant as both a main and interaction effect, but task experience adds little to the explanatory power of the Maintenance Tool Utilization Model. These results support the value of improved CASE tool training programs.
-
The Effect of Task and Tool Experience on Maintenance CASE Tool Usage
Information Resources Management Journal, 2003Co-Authors: Mark T. Dishaw, Diane M. StrongAbstract:Computer-aided software engineering CASE tools have been advocated for improving maintainer productivity and the quality of maintained software. While there is evidence that such benefits can accrue to organizations adopting maintenance-oriented CASE tools, a key problem in achieving the desired benefits from CASE tools is low usage of these tools by programmers. The previously tested Maintenance Tool Utilization Model was a first step in investigating the factors that affect whether maintainers choose to use CASE tools during maintenance Projects. We test the addition of experience with software maintenance tools and with the software maintenance task to the Maintenance Tool Utilization Model. The role of experience is important because managers can provide training to increase experience and they can ensure that Project teams have some members experienced with the tools or with the task. Data for the test are collected from software maintainers working on their organization's normal maintenance Project Backlog. Tool experience is significant as both a main and interaction effect, but task experience adds little to the explanatory power of the Maintenance Tool Utilization Model. These results support the value of improved CASE tool training programs.
Ralph Hughes - One of the best experts on this subject based on the ideXlab platform.
-
Redefining the Epic Stack to Enable Value Accounting
Agile Data Warehousing for the Enterprise, 2020Co-Authors: Ralph HughesAbstract:Enterprise data warehousing team leaders can employ two techniques to make their Project Backlogs clear and well aligned with their company’s business needs. First, a codified epic decomposition framework will strongly type the stories in the Backlog, giving a distinct purpose to epics, themes, and user stories. Teams can utilize this requirements typing to define and refine items on the Project Backlog until they pass DILBERT’S test, indicating that they are good enough to allow programming to begin. Second, the practice of “value accounting” will ensure that all requirements trace to clear expressions of business need. Value accounting allocates the sponsor’s statement of application benefits downward to the epics, themes, and user stories of the Project Backlog. It also enables team leaders to quantify the contribution they have made to the company with every subrelease in a way that stands up to stakeholder scrutiny and builds excitement and greater business participation in the Project.
-
Artifacts for the Generic Requirements Value Chain
Agile Data Warehousing for the Enterprise, 2015Co-Authors: Ralph HughesAbstract:Agile enterprise data warehousing developers need to actively participate in shaping a Project Backlog so that if their product owner struggles with his leadership role, they can guide him in defining Project requirements. Developers can actively participate in defining and validating the requirements of their Projects using several context-defining artifacts commonly used by generic agile teams, such as mind maps, vision boxes, vision statements, and product roadmaps. These generic agile requirements artifacts prompt the product owner to think more deeply about the application being requested so that she can provide a dependable and coherent stream of user stories. They also enable teams to avoid pursuing the wrong Project concept by prompting them to regularly consider whether they are overlooking simpler solutions or hidden complexity in the business needs. These artifacts also communicate well the Project’s direction and delivery time frames, making the entire endeavor more transparent to outside stakeholders.
-
Deriving Initial Project Backlogs
Agile Data Warehousing Project Management, 2013Co-Authors: Ralph HughesAbstract:An initial Project Backlog of user stories is essential to getting an agile warehousing Project started. Stories on the initial Backlog should come from the product owner and sometimes a couple of other key user groups. Since the initial Backlog allows Project estimation, and estimation in turn supports Project funding, these stories often have to be gathered before Iteration 0 of the sprint and before the full team is assigned. A Project architect is a good choice for leading this preProject effort. He should declare an Iteration −1 to create the time to gather the initial Project Backlog. In addition to that Backlog, the architect will also want to derive from the initial interviews a business target model of the fact and dimensional entities needed to solve the product owner’s analytical problem. This model will support later the work of the data architect and systems analysts during the Project’s Iteration 0.
Hironori Washizaki - One of the best experts on this subject based on the ideXlab platform.
-
QA to AQ part four: shifting from quality assurance to agile quality: prioritizing qualities and making them visible
2015Co-Authors: Joseph W. Yoder, Rebecca Wirfs-brock, Hironori WashizakiAbstract:As organizations transition to agile processes, Quality Assurance (QA) activities and attention to system quality need to evolve along with the evolution of development practices. Agile quality teams incrementally deliver working software while ensuring that important system qualities are also addressed. In order to pay appropriate attention to system qualities, they need to be visible and included as part of the prioritized work. This paper presents patterns for identifying system qualities and including them on the Project roadmap, adding quality-related work items to the Project Backlog, and creating a quality radiator that communicates the status and goals for delivering system qualities.
Lisa Loftusotway - One of the best experts on this subject based on the ideXlab platform.
-
assessment of txdot staffing for Project development and construction and Project Backlog analysis
2013Co-Authors: Khali R Persad, Robert Harrison, Nabeel Khwaja, Lisa LoftusotwayAbstract:The objective of the work documented in this report was to examine full-time-equivalent (FTE) staffing needs for Texas Department of Transportation (TxDOT) Project development and construction, and analyze needs for Backlogging Projects, i.e., preparing construction plans in advance and keeping them at the ready for possible construction funding in the future. As TxDOT developed its long-term Project development plans (PDP-2012 and PDP-2013), the research team provided support to the respective TxDOT task forces. In fiscal year (FY) 2011, the research team examined FTE needs for TxDOT Project development and construction, and began to analyze needs for Backlogging Projects. In FY 2012 this work was continued to complete analyses requested by TxDOT as a result of additional complexities identified during development of PDP-2012, and to address changes in funding enacted by the 82nd Texas Legislature.
