Welcome!
Hi! I'm Darryl Bartlett. Thanks for dropping by to see my personal project.I'm a Certified Associate in Project Management (CAPM)® by the Project Management Institute.This personal project is to show a little bit of how I organize, communicate, and structure my work, my thinking, and myself.You can use the buttons below to navigate this site...
- Summary: A quick overview of my project.
- Details: More detail about what and how I'll be working through the project.
- Progress: Updates and communications I've done and continue to do throughout the project.If you're interested in contacting me to talk about how I can help your team with project management tasks, you can click the Contact button below for my LinkedIn or Email.Thanks for coming by and taking a look. I'm looking forward to connecting with you soon!
Project Summary
| Project Title: | The 100 Day Python Project |
| Problem Statement: | Learning how to write code with Python in 100 days (100 lessons). |
| Solution Approach: | Using a combination of traditional project management and Agile framework. This includes: using the structure of a coding course in Python, daily scrums for progress, and retrospectives for lessons learned. |
| Key Results: | Note: This project is currently in progress. Results and milestones will be added throughout the project. |
| Timeline: | Approx. 100 days. Key milestones will be at each phase completion. Phases include: Beginner, Intermediate, Intermediate+, Advanced, and Portfolio Projects. |
Why I Picked a Software Project?
I like the idea of working on a hybrid project.
Predictive Project Management: The structure of a coding course is setup with each step building towards the next one. Each step is completed in sequence.
Agile Framework: By using iterations while coding, it gives me the ability to make adjustments, if needed. Even though it's "100 days of coding", some days may be done quickly and others may take longer.
The Challenge: Not only do I get to work on a personal project management project, I'm also learning something I'm interested in. It will become more challenging the deeper I get into the project.
Project Details
This is a breakdown of how I'm managing tasks throughout the project. As I learn more about the project, I'll update this section where needed.
Project Scope & Objectives
| Primary Objective: | Learn how to program in Python using the "100 Days of Code™: The Complete Python Pro Bootcamp" course. |
| Secondary Objectives: | 1. Use an Agile Framework, Kanban, and MS Project. 2. Learn in public by posting progress on LinkedIn. 3. Build 100 projects using Python. |
| Success Metrics: | 1. Completion of each milestone/phase - Beginner thru to Portfolio Projects. 2. Completion of all 100 days. 3. Ability to write my own Python programs. |
| Constraints: | 1. Time: 100 Days of coding - approx. one project per day. 2. Resources: I'm the only resource, meaning I'm playing multiple roles in the project. |
Stakeholder Management
| Project Sponsor: | Darryl Bartlett |
| Key Stakeholder: | Course Instructor: Angela Yu - She would like to see her students complete the 100 Days and become a pro developer. |
| Communication Strategy: | 1. "Daily standups" for each coding Day. 2. Retrospectives after each iteration of 10 days. 3. Posting progress on LinkedIn. |
Project Planning & Execution
| Timeline: | 1. 100 coding days. 2. Milestones for each phase of the project: * Beginner * Intermediate * Intermediate+ * Advanced * Portfolio Projects |
| Resource Allocation: | 1. Team Member: Darryl Bartlett 2. Tools: PyCharm IDE, Python installation, Internet for course access, laptop, computer monitor, mouse, Trello, MS Project, MS Excel. 3. Budget: Minor cost for the Python course. |
| Risk Management: | 1. Software: Any issue causing PyCharm or Python not to work properly - this would involve researching any error messages, doing any necessary updates, contacting support, or potentially switching to other software. 2. Hardware: Any issue to hardware equipment, such as the laptop - a secondary laptop (or other accessories) would need to be considered and updated with the necessary software, if needed. 3. Time to complete each lesson day: Some lessons may be completed faster than others depending on the type of assignment, learning speed, and/or understanding of the lesson - this could affect the planned time for completion and an adjustment to the timeline would need to be considered. 4. Coding Errors: If a coding error causes a setback towards the completion of a lesson, time will be needed to learn about the issue and how to correct it - including using Google search, Stack Overflow, Python.org, developer forums. 5. Other learning resources: If something needs to be learned outside of the course material, then other resources will need to be researched that can help produce a solution. |
| Change Management: | Changes may be made throughout the project while using the Agile framework. For example: if a change needs to be made to the programming environment, the change will be made as soon as possible to continue with a course assignment or project. |
Results & Impact
| Quantitative Results: |
| Qualitative Benefits: |
| Lessons Learned: |
| Recommendations: |
Project Progress
Select available Sprint buttons to see Daily Scrum and Retrospective notes.
Note: Daily Scrum notes refer to a completed course "Day" of coding including video lessons and/or readings, assignments, and a project.
Sprint 1 - Days 1 to 10
This first sprint was used as a testing ground. Therefore, there are no Daily Scrums. Since this is part of the Beginner Phase of the course, I wanted to complete the first 10 Days as a way to understand how the course is structured. It has given me a good foundation for how to manage the project starting in the next sprint.
Retrospective
Sprint 2 - Days 11 to 20
Daily Scrum - Day 11
Daily Scrum - Day 13
Daily Scrum - Day 15
Daily Scrum - Day 17
Daily Scrum - Day 19
Daily Scrum - Day 12
Daily Scrum - Day 14
Daily Scrum - Day 16
Daily Scrum - Day 18
Daily Scrum - Day 20
Sprint 3 - Days 21 to 30
Sprint 4 - Days 31 to 40
Sprint 5 - Days 41 to 50
Sprint 6 - Days 51 to 60
Sprint 7 - Days 61 to 70
Sprint 8 - Days 71 to 80
Sprint 9 - Days 81 to 90
Sprint 10 - Days 91 to 100
Contact
If you're interested in contacting me to talk about how I can help your team with project management tasks, you can find me on LinkedIn or send me an Email.