-
Notifications
You must be signed in to change notification settings - Fork 568
Productivity Initiative
Software quality is certainly impacted by team-based processes, practices and tools. Even so, each line of source is produced by a person. The Productivity++ checklist is meant as a reminder to each person on the team to confirm that the work to be started right now is the right thing to do and is being done right.
When you start a work session, ask the question, Is my work [Traceable, In Progress, Sustainable, Improved]?
- Traceable:
- Task is planned and recorded in the Trilinos GitHub issues database.
- Task is traceable back to core requirements.
- Stretch: There are specification and design artifacts for this task.
- In Progress:
- In the context of a Kanban workflow [Minibook][YouTube], this task is the most effective use of my time.
- This task is listed in the “In Progress” column of the Trilinos Kanban board.
- My “In Progress” queue size is within personal or small group limit.
- Stretch: Backlog has been recently scanned and refined (groomed).
- Sustainable:
- Output is high quality work, usable until the end of its expected life.
- Testing is sufficient for confident refactoring in the future.
- Stretch: Code, including test suite and associated documentation, is good enough for someone else to support after I move on to other work.
- Improved:
-
The quality of my work better than six months ago:
- More consistent programming discipline.
- Learned new skills.
- Read literature, took on-demand or in-person training courses.
Contact Mike Heroux [email protected]
Kanban and Scrum -- Making the Most of Both, by Henrik Kniberg and Mattias Skarin
Copyright © Trilinos a Series of LF Projects, LLC
For web site terms of use, trademark policy and other project policies please see https://lfprojects.org.
Trilinos Developer Home
Trilinos Package Owners
Policies
New Developers
Trilinos PR/CR
Productivity++
Support Policy
Test Dashboard Policy
Testing Policy
Managing Issues
New Issue Quick Ref
Handling Stale Issues and Pull Requests
Release Notes
Software Quality Plan
Proposing a New Package
Guidance on Copyrights and Licenses
Tools
CMake
Doxygen
git
GitHub Notifications
Mail lists
Clang-format
Version Control
Initial git setup
'feature'/'develop'/'master' (cheatsheet)
Simple centralized workflow
Building
SEMS Dev Env
Mac OS X
ATDM Platforms
Containers
Development Tips
Automated Workflows
Testing
Test Harness
Pull Request Testing
Submitting a Pull Request
Pull Request Workflow
Reproducing PR Errors
Addressing Test Failures
Trilinos Status Table Archive
Pre-push (Checkin) Testing
Remote pull/test/push
PR Creation & Approval Guidelines for Tpetra, Ifpack2, and MueLu Developers