These choices are the interesting part of programming. People talk about persistence as something that you acquire.
- I am not mean, I am Honest;
- The Sixth Lamentation (Father Anselm Novels Book 1).
- Sol Detente (Spanish Edition).
- Tentation Nocturne (HQN) (French Edition).
- 1. Lessons Learned Report:;
With practice, comes persistence. But, in truth, if you program long enough, it becomes a part of you. You become a person who simply never quits. Persistence is also not a destination. Instead, the act of programming calls for persistence. If you want to get it done, you simply have to be persistent. Before finding programming, I already loved learning many subjects. I was a science kid who was curious about science and loved the theories.
Through programming, I learned the pathways of learning. I have a formula for myself to learn many new skills. I have applied this formula successfully to learning about many skills. This is why programming is an exercise to help you come up with your plan of learning.
I have encountered many difficult hurdles in programming. Many times, I had ah-ha moments thinking about my problems while I went about my day-to-day activities. Quickly, you learn where inspiration, motivation, and creativity comes from in dealing with difficult problems.
Lessons Learned Template - Project Management Docs
You appreciate those difficult problems that allows you to journey the path of creative thinking. Programming is inherently problem-solving. But, the process is important. You start with what you need to implement. You design your first draft of implementation. You implement.
Knowledge Management Reference
Then, you revise. Once you are done, you test. The process is very clear for solving all your problems. You simply have to follow through.
After programming for a while, I start to see myself doing this with the problems I encounter in life. Steve Jobs said that programming teaches you how to think. Programming is composed of asking questions, creating solutions, try and fail, and try again to reach a kind of orderly beauty in your implementations. The process and the questions that you ask along the way inform the way that you think about objects, storage, functions, and expressions.
The painting is a reflection of your thoughts. So, is the program. To me, programming is the process of gaining invaluable life skills. As a young adult, having learned programming early in my life helped me with the business skills I gained later. It also helped me navigate my personal life. In a sense, through programming, you discover parts of yourself that you apply to all aspects of life.
What are you waiting for? About the Author. She has a background in programming and statistics. On her spare time, she writes poetry and blogs on her website.
- Knowledge Management Processes.
- Why And How To Document Lessons Learned (With Lessons Learned Template).
- The Husband She Never Knew (Mills & Boon Modern).
- John Crust and Snuffling Pig;
- A Sermon Series On Worship (The Power Of Worship)?
- Lessons Learned Quotes.
- Lessons Learned - do it Early, do it Often.
Subscribe to my weekly newsletter to stay connected. Sign in.
Browse By Tag
Get started. Top Story Medium Things Submit. Life Lessons Learned As a Programmer. Any young adult can benefit from having some programming experience. Jun Wu Follow. They are moments of true acceptance. Innovative approaches and good work practices can be shared with others. Lessons learned can be used to improve future projects and future stages of current projects. It is not necessary to wait until the end of the project for the learning to occur. Lessons can be identified at any point during the project.
A lessons learned session should be conducted at different time frames based on the criticality and complexity of the project. Key times are at the end of the project, at the end of each phase and real time — when you learn the lesson. If you wait until the end the project for a large project you miss some of the key lessons. Because of the time that has elapsed, project team members may forget some of the things they learned or team members assigned to the project in the early phases may no longer be part of the project during the later phases.
The best time to begin discussing lessons learned is during the project kick-off meeting. At level 1 organizations are not routinely capturing lessons learned partly because there is no defined process in place. Lessons learned are handled on a project by project basis with no standardized tools or consistency among projects. At a minimum level 1 organizations may have a meeting where lessons learned are discussed and produce a report summarizing the findings. This report is then shared with the immediate project stakeholders. The purpose of a lessons learned process is to define the activities required to successfully capture and use lessons learned.
The lessons learned process shown in Exhibit 1 includes five steps: identify, document, analyze, store and retrieve. These steps are consistent for all three levels; however, the tools and techniques become more involved with each level. Regardless of the level, it is important for the team to view lessons learned as constructive. Leadership should encourage project stakeholders to use the process, tools and results. Step 1 of the lessons learned process is to identify comments and recommendations that could be valuable for future projects.
The two activities for identifying lessons learned are: 1 prepare for lessons learned session and conduct lessons learned session. The person who will be facilitating the lessons learned session should prepare in advance. In preparation for the lessons learned session the facilitator should have the participants complete a project survey.
The project survey will help the participants to be better prepared to respond during the lessons learned session and will also give them the opportunity to provide input if they are unable to attend. The project survey should be organized by category. The use of categories will ensure key information is not missed and will later help to focus the discussion. Standard categories for each project should be defined and additional categories specific to a project can be added. Suggested categories include project management, resources, technical, communication, business processes, requirements, design and build, testing, implementation and external areas.
These categories can be subdivided into more detailed categories. For example, project management can be divided into the process groups: initiating, planning, executing, monitoring and controlling and closing. Planning can then be further divided into project schedule, risk analysis, etc. A simple approach is to begin with a few categories such as project management, resources, technical and external areas and then add more categories as needed. The project survey should also include specific questions for each category.
- Virtudes del Indio / The Virtues of the Indian.
- Touchy Subjects.
- Explore Lessons Now.
- The Power to Heal.
- 1. Lessons Learned Report:!
- Lessons Learned Quotes ( quotes).
These responses will be used by the lessons learned facilitator to guide the discussion during the lessons learned session. Three key questions should be included as part of the survey: 1 what went right, 2 what went wrong and 3 what needs to be improved.