Don't leave a work package half-finished!
Article#: 00009
Date: 2020-04-19
Author: Radim
Only switch to another work package when the one you have been working on is completely finished.
Other work packages that are dependent would later be affected by the incompleteness.
Don't say "we'll do it later"!
Do not leave any part or feature of the work package incomplete or out! (e.g. code comments, documentation, safety measures, correct design, handling unusual situations, etc.)
It takes longer to understand the details of the work package later, and it is more difficult to complete the work package with the same quality.
Perhaps the original staff will no longer be available later and the information about the upcoming tasks may also be missing.
Usually other important things have to be done "later" and there is no chance of completing the unfinished work package any more.
It is better to do the work package in one go, because in reality the phrase "THAT WE WILL DO LATER" can come out as "THAT WE WILL DO NEVER".
© Radim-Automation, 2020–2026. All rights reserved.
Sharing of this article is permitted with proper attribution (link to the original page).
Related previous articles:
Related next articles:
- Check the result!
- Get and stay in the flow!
- Realize every good idea ASAP!
- Define test scenarios and test cases continuously!
- Do the right things and do them right!
- Safety first!
- More than just start and stop
- I can see what you can not see
- Store email messages in the project folder!
- Do you really want to start with this?
- Is the way really the goal?
- Prepare a good project plan and keep it up to date!
- HMI and PLC applications should grow together
- Write down your best practices and processes!
- Set your goals for today, tommorow, this week ...
- Are the people planned for this task really available?
- Appoint a representative!
- Who knows it?
- Write and accept only readable code!
- Use a usefull styleguide!
- Functional and intuitive HMI
- Who will operate?
- Why do automation projects fail?
- Project leader
- Learn from your journey!
- Design machines with a focus on user's abilities and needs
- Think critically!
- Are there also any disadvantages?
- Modular software architecture
- Machine modularization
- Knowledge gained from a completed project is priceless
- Variable names
- Visual modeling
- Documentation issues
- Clear signals
- Event logger as the very first function implemented in the program
- My boss was a hero
- Version control system
- Keep the documentation up to date throughout the project
- Make backups, make small changes and test a lot
- High Performance HMI
- HMI - Have a consistent style
- Hidden dangers during commissioning
- The false illusion of rapid progress
- Redundant PLC – Yes or No?
Comment#: 00002
Date: 2020-04-19
User:
Based on "Agile development" work packages should be achievable within one Sprint.
Comment#: 00003
Date: 2020-04-20
User: Radim
@Comment#: 00002
I think it's a great rule to break the project down into small tasks so that every such a task can be fully completed within a few days at most.
But what does "fully completed" mean?
Completely designed, developed, tested, successfully installed and running at the customer ...?
Are multiple iterations considered?
Comment#: 00004
Date: 2020-05-18
User: Radim
What you can do today, don't put off until tomorrow, because you don't know what will stop you from doing it tomorrow.
Comment#: 00005
Date: 2021-01-11
User: Radim
One of the reasons why you stop having fun is the accumulation of problems and unfinished tasks.
Comment#: 00006
Date: 2022-11-16
User: Radim
"The later in the development cycle we discover a bug in the software, the more expensive it is to fix."
- https://www.linkedin.com/pulse/unit-testing-world-industrial-automation-jakob-sagatowski/?trackingId=8Il2af6t8cNMxCT2pRn76Q%3D%3D
Comment#: 00007
Date: 2022-11-30
User: Radim
New problems occur in real operation that were not expected or experienced during development or test operation.
Then you are happy if you know the system / devices well, if you know how they work, how they are connected and controlled, etc. This know-how comes simply from working on the system, from solving smaller and larger problems...
Comment#: 00008
Date: 2022-11-30
User: Radim
During development, do not use other (preliminary) hardware than the one selected for production. You gain important experience with the hardware. You will find out whether the performance is sufficient and learn how to eliminate problems that arise during development. If the software development phase is carried out on the hardware designed for sharp operation, you will experience fewer unpleasant surprises after the machine is commissioned.
Comment#: 00009
Date: 2022-12-01
User: Radim
"It's better to break down the tasks into several smaller steps that you can complete. This gives you a sense of accomplishment and motivates you to keep going. Too many open projects and "loose ends", on the other hand, cause conscious or unconscious stress and do not allow your brain to rest."
Translated from:
- Gabriele Thies. 8 Wege, um deine Aufgaben sinnvoll zu strukturieren.
- https://www.gabrielethies.de/blog/aufgaben-sinnvoll-strukturieren
Comment#: 00010
Date: 2022-12-15
User: Radim
There is a big difference between "done" and "done". The "done" status of a task in Excel or on a to-do list does not always mean that it makes sense, works, is understandable and has been confirmed by a test.
Comment#: 00011
Date: 2023-06-08
User: Radim
"Today, technical debt, also known as tech debt and code debt, usually occurs when development teams choose to write speedy code while building new features of a software development product. Speedy code delivery can help your team meet deadlines, and the debt you accrue may be worth it, though it could also lead to negative outcomes if managed incorrectly. These negative outcomes aren’t always avoidable once the decision to accrue technical debt has been made."
- https://asana.com/resources/technical-debt
Comment#: 00013
Date: 2023-08-17
User: Radim
Why is there never enough time to do it right the first time, but always enough time to do it over?
"The saying "There's never enough time to do it right the first time, but always enough time to do it over" reflects a common observation about human behavior and project management. It suggests that people often rush through tasks or projects initially, hoping to save time and effort, but end up making mistakes or producing subpar results. As a result, they eventually need to invest more time and resources to fix those mistakes or redo the work properly.
There are several reasons why this phenomenon occurs:
1. Underestimation of Complexity: People might underestimate the complexity or difficulty of a task or project at the outset. This can lead to inadequate planning and allocation of resources, resulting in mistakes or oversights.
2. Pressure to Meet Deadlines: There is often pressure to complete tasks or projects quickly to meet deadlines. This can lead to shortcuts being taken or important steps being skipped in the interest of saving time.
3. Lack of Attention to Detail: When rushing through a task, individuals might not pay enough attention to details, leading to errors that require corrections later.
4. Overconfidence: Sometimes, people might overestimate their abilities or knowledge, leading them to believe they can complete a task quickly without proper preparation or diligence.
5. Incomplete Information: In some cases, tasks or projects might be started without having all the necessary information or requirements. This can lead to incorrect assumptions and decisions.
6. Limited Resources: Constraints on resources such as time, money, or manpower might force people to cut corners initially, with the intention of fixing things later when more resources are available.
7. Learning Curve: Sometimes, tasks involve new skills or technologies that individuals need to learn along the way. Initial attempts might be suboptimal as people are still acquiring the necessary expertise.
The saying serves as a reminder that investing the necessary time and effort upfront to do a task properly can save more time and resources in the long run. Proper planning, attention to detail, and thorough execution can help prevent mistakes and the need for redoing work.
However, it's worth noting that the saying is not universally true. In some cases, rushing through tasks might yield acceptable results, and redoing work might not be necessary. It all depends on the nature of the task, the level of expertise involved, and the specific circumstances."
- https://chat.openai.com (Why is there never enough time to do it right the first time, but always enough time to do it over?)
Comment#: 00014
Date: 2023-10-04
User: Radim
"Never discourage anyone who continually makes progress, no matter how slow."
- Plato
Comment#: 00015
Date: 2024-03-25
User: Radim
Remove the "ballast" from the program!
Only include things in the program that are really needed. Unnecessary parts of the code in the program become obsolete, untested, raise unnecessary questions and are a source of ambiguity.
Sometimes it is a good idea to try more than one way in practice to find out which way is the best. However, once we have decided on a particular approach, it is important to consolidate our methods and remove the outdated ones. By removing "ballast" from the program, we eliminate potential sources of confusion and improve the overall quality of the code.