Professional Development: Exploring IS Careers
🎓 Student Information
Student Name: Alexis Pinon
Course: Managing IT Projects
Semester: Fall 2025
📋 1. Project Title & Description
Project Title: Exploring IS Careers
Description: In order to explore careers in IS, I will create a digital portfolio to develop my current skills, tools, and experience. Additionally, I will pursue new certifications and small projects to add to a digital portfolio website that I will create. These elements, along with reflections on my work, will work toward helping me decide what career in the information systems field will best suit me.
🎯 2. Vision, Mission & Strategy Alignment
Personal Mission Connection: This project connects to my mission directly, by improving my skills as well as focusing on creating a user-focused solution to my current problem of a lack of demonstrated experience in information systems.
Vision Alignment: This project aligns with my vision in that it allows me to start working on a project that is impactful in my own life, giving me experience that I will then be able to use when doing the same for others.
Strategic Goal Support: This project advances my strategic goal of developing skills in database administration and project management. It also fits into my bigger picture of exploring what careers I would do well in.
💼 3. Business Case & Justification
Professional Value: This project will help me professionally by pushing me to get industry recognized certifications, enhancing my resume and eventually the completed digital portfolio.
Personal Value: I will gain personal value by practicing new skills such as website design/development. It will also give me personal value by helping me decide what careers to pusue.
Learning Outcomes: From this project, I'll learn specific technical skills like creating a website from scratch, I'll gain practical project management skills, and I'll increase my knowledge through the certifications I intend to complete.
🗺️ 4. High-Level Scope
✅ In Scope
- An HTML website that shows my projects, certificates, work experience, and about me.
- 1–2 projects that can be completed in a week or two:
- Small DB work (coding, architecture… something like my 4580 project)
- Data visualizations (Tableau, Power BI) – related to form "be part of the stats" (industry, rate the page…)
- Descriptions of previous projects (JPL/Oracle experience)
- Mobile functionality
- Create design for webpage
🗺️ Roadmap Items
- SEO
- Integration with business cards (NFC)
- Further development with certificates
- Design a comprehensive database and app from ground up to showcase skills
❌ Out of Scope
- Specifics of discreet projects
- Irrelevant work/generic projects
- Extensive website functionality (it doesn't need to be the most intricate site ever)
- Irrelevant technical skills
- Examples of work with less than stellar outcomes
👥 5. Stakeholder Register
| Stakeholder | Category | Role/Interest | Power | Interest | Engagement Strategy |
|---|---|---|---|---|---|
| Family | External | High Power, High Interest; Manage Closely | H | H | Regular updates on progress and setbacks; listen to opinions for project and education decisions. |
| Professional Contacts | External | High Power, Low Interest; Keep Satisfied | H | L | Engage when needed, especially for big decisions and resources. |
| Peers | External | Low Power, Low Interest; Monitor | L | L | Passive communication; little to no decision-making power. |
| Current Employer | External | Low Power, High Interest; Keep Informed | L | M | Keep informed on changes; open to input and consultation for big changes. |
| Mentors | External | High Power, Low Interest; Keep Satisfied | M | M | Engage as needed for advice and big decisions. |
| Friends | External | High Power, High Interest; Manage Closely | H | H | Regular updates on progress and setbacks; listen to opinions for project and education decisions. |
| Open-source Communities/Contributors | External | Low Power, Low Interest; Monitor | L | L | Passive communication. |
| Professors | Internal | High Power, Low Interest; Keep Satisfied | H | M | Engage when needed, especially for big decisions and resources. |
| Certificate/Software Vendors | Regulatory | Low Power, Low Interest; Monitor | L | L | Passive communication. |
Power-Interest Grid Visualization
| Keep Satisfied Professors Professional Contacts Mentors |
Manage Closely Family Friends |
| Monitor Peers Certificate/Software vendors |
Keep Informed Current Employer |
📦 6. Deliverables
| Deliverable | Definition of Done |
| Certification: Oracle/Project Management Certification – evidenced by official certificates. | Completed courses or exams Certificates from the companies |
| Database Project: 1–2 week project demonstrating relational DB and app. | When completed, I will have an app to add to my digital portfolio that has a database in the background that can be manipulated by visitors to the website. |
| Website Design: Figma mockups and design standards. | A Figma frame with the design elements Another frame with mock-ups of the different types of webpages. |
| Digital Portfolio Website: HTML/CSS site hosted online. | A completed website that can be clicked through and has clear navigation and pages. |
| Mobile Functionality: Website optimized for mobile devices. | When completed, the digital portfolio will be viewable on laptop/desktop and mobile devices. |
| Business Analysis: An analysis of a business's practices and areas for optimization. | The end result will be an analysis for a business that they can use to take action to improve an area of their operations. |
🧩 7. Work Breakdown Structure
| WBS ID | Level | Task/Work Package Name | Duration | Dependencies (WBS ID & Name) | Parallel |
|---|---|---|---|---|---|
| ▾ 1 | Deliverable | Design the website | 14 days, 8 hours | -- | |
| 1.1 | Work Package | Plan the design | 3 days, 2 hours | ||
| 1.1.1 | Task | Research common digital portfolios | 2 days | -- | |
| 1.1.2 | Task | Identify best practices | 2 hours | 1.1.1 Research common digital portfolios | |
| 1.1.3 | Task | Decide on layout and color | 1 day | 1.1.2 Identify best practices | |
| 1.2 | Work Package | Mock ups | 9 days | -- | |
| 1.2.1 | Task | Create lo-fi wireframes | 2 days | 1.1.3 Decide on layout and color | Create UI components frame |
| 1.2.2 | Task | Get feedback on basic design | 2 days | 1.2.1 Create lo-fi wireframes | |
| 1.2.3 | Task | Create UI components frame | 1 day | 1.2.2 Get feedback on basic design | Create lo-fi wireframes |
| 1.2.4 | Task | Create hi-fi wireframes | 3 days | 1.2.3 Create UI components frame | |
| 1.2.5 | Task | Get feedback on design and content placement | 2 days | 1.2.4 Create hi-fi wireframes | |
| 1.3 | Work Package | Functionality | 3 days, 6 hours | -- | |
| 1.3.1 | Task | Create user flows | 1 day | 1.2.5 Get feedback on design and content placement | Create lo-fi wireframes |
| 1.3.2 | Task | Get feedback on flows | 2 days | 1.3.1 Create user flows | |
| 1.3.3 | Task | Update flows if necessary | 6 hours | 1.2.5 Get feedback on design and content placement | |
| ▾ 2 | Deliverable | Create an HTML/CSS-based website for my digital portfolio | 6 days, 6.5 hours | -- | |
| 2.1 | Work Package | HTML Structure | 2 days, 12 hours | -- | |
| 2.1.1 | Task | Plan the structure based on finalized design | 6 hours | 1 Design the website | Plan the details of customization and functionality |
| 2.1.2 | Task | Write HTML | 2 days | 2.1.1 Plan the structure based on finalized design | Write CSS/JavaScript |
| 2.1.3 | Task | Push to github and deploy site | 1 hour | 2.1.2 Write HTML | |
| 2.1.4 | Task | Troubleshoot for errors in code | 1 hour | 2.1.3 Push to github and deploy site | Troubleshoot for errors in code |
| 2.1.5 | Task | Correct errors if necessary | 4 hours | 2.1.4 Troubleshoot for errors in code | Correct errors if necessary |
| 2.2 | Work Package | CSS/JavaScript | 6 days, 5.5 hours | -- | |
| 2.2.1 | Task | Plan the details of customization and functionality | 1 day | 1 Design the website | Plan the structure based on finalized design |
| 2.2.2 | Task | Write CSS/JavaScript | 3 days | 2.2.1 Plan the details of customization and functionality | Write HTML |
| 2.2.3 | Task | Update github | 0.5 hour | 2.2.2 Write CSS/JavaScript | |
| 2.2.4 | Task | Troubleshoot for errors in code | 1 hour | 2.2.3 Update github | Troubleshoot for errors in code |
| 2.2.5 | Task | Correct errors if necessary | 4 hours | 2.1.2 Troubleshoot for errors in code | Correct errors if necessary |
| 2.2.6 | Task | Expand upon existing site with more integration | 2 days | 2.2.4 Correct errors if necessary | |
| ▾ 3 | Deliverable | Mobile functionality of the website | 9 days, 4.5 hours | -- | |
| 3.1 | Work Package | Design and Mock ups | 4 days, 20 hours | -- | |
| 3.1.1 | Task | Using previous research, decide how to format mobile view | 2 hours | 1.1.3 Decide on layout and color | |
| 3.1.2 | Task | Create lo-fi wireframes | 6 hours | 3.1.1 Using previous research, decide how to format mobile view | |
| 3.1.3 | Task | Get feedback on basic design | 2 days | 3.1.2 Create lo-fi wireframes | |
| 3.1.4 | Task | Create UI components frame | 4 hours | 3.1.3 Get feedback on basic design | |
| 3.1.5 | Task | Create hi-fi wireframes | 8 hours | 3.1.4 Create UI components frame | |
| 3.1.6 | Task | Get feedback on design and content placement | 2 days | 3.1.5 Create hi-fi wireframes | |
| 3.2 | Work Package | Updating | 4 days, 8.5 hours | -- | |
| 3.2.1 | Task | Create code for mobile functionality | 2 days | 3.1.6 Get feedback on design and content placement | |
| 3.2.2 | Task | Get feedback on initial mobile version | 2 days | 3.2.1 Create code for mobile functionality | |
| 3.2.3 | Task | Check for errors/inconsistencies in pages | 2 hours | 3.2.2 Get feedback on initial mobile version | |
| 3.2.4 | Task | Adjust code | 6 hours | 3.2.3 Check for errors/inconsistencies in pages | |
| 3.2.5 | Task | Update github | 0.5 hour | 3.2.4 Adjust code | |
| ▾ 4 | Deliverable | Certification in Key Recognized areas | 3 weeks, 12 hours | -- | |
| 4.1 | Work Package | Plan certificates | 13 hours | -- | |
| 4.1.1 | Task | Research which certificates would be most beneficial | 6 hours | -- | Research funding possibilities |
| 4.1.2 | Task | Identify where to obtain the certs | 2 hours | 4.1.1 Research which certificates would be most beneficial | Identify any costs of certs |
| 4.1.3 | Task | Identify any costs of certs | 1 hour | 4.1.2 Identify where to obtain the certs | Identify where to obtain the certs |
| 4.1.4 | Task | Research funding possibilities | 4 hours | 4.1.3 Identify any costs of certs | Research which certificates would be most beneficial |
| 4.2 | Work Package | Preparing for cert exams | 4 weeks, 4 hours | -- | |
| 4.2.1 | Task | Research what sorts of topics will be on the exams | 2 hours | 4.1.4 Research funding possibilities | Research which certificates would be most beneficial |
| 4.2.2 | Task | Take courses associated with certifications | 2 weeks | 4.2.1 Research what sorts of topics will be on the exams | Study/practice for exams |
| 4.2.3 | Task | Study/practice for exams | 2 weeks | 4.2.2 Take courses associated with certifications | Take courses associated with certifications |
| 4.2.4 | Task | Plan times to take certs | 2 hours | 4.2.3 Study/practice for exams | |
| 4.3 | Work Package | Complete certificates | 1 week, 2 hours | -- | |
| 4.3.1 | Task | Take exams | 1 week | 4.2.4 Plan times to take certs | |
| 4.3.2 | Task | Complete any documentation necessary to get certs | 2 hours | 4.3.1 Take exams | |
| ▾ 5 | Deliverable | 1-2 small database projects | 3 days (per project) | -- | |
| 5.1 | Work Package | Planning | 2 days, 4 hours | -- | |
| 5.1.1 | Task | Conduct research on short-term achievable projects | 2 days | -- | |
| 5.1.2 | Task | Decide what database platform to use | 1 hour | 5.1.1 Conduct research on short-term achievable projects | |
| 5.1.3 | Task | If possible, identify a beneficiary of the database | 2 hours | 5.1.2 Decide what database platform to use | Identify primary and foreign keys |
| 5.1.4 | Task | Identify primary and foreign keys | 1 hour | 5.1.2 Decide what database platform to use | If possible, identify a beneficiary of the database |
| 5.1.5 | Task | Plan standardizes naming of database elements | 1 hour | 5.1.4 Identify primary and foreign keys | |
| 5.2 | Work Package | Create | 17 hours | -- | |
| 5.2.1 | Task | Write queries for tables, columns, and constraints | 4 hours | 5.1.5 Plan standardizes naming of database elements | Draft sample data |
| 5.2.2 | Task | Draft sample data | 4 hours | 5.2.1 Write queries for tables, columns, and constraints | Write queries for tables, columns, and constraints |
| 5.2.3 | Task | Validate dataset values | 1 hour | 5.2.2 Draft sample data | |
| 5.2.4 | Task | Write queries to insert sample data | 2 hours | 5.2.1 Write queries for tables, columns, and constraints | Add comments for query logic |
| 5.2.5 | Task | Verify successful data upload | 0.5 hour | 5.2.4 Write queries to insert sample data | |
| 5.2.6 | Task | Write queries for any updates that need to be made | 2 hours | 5.2.5 Verify successful data upload | Test queries/database |
| 5.2.7 | Task | Add comments for query logic | 1 hour | 5.2.1 Write queries for tables, columns, and constraints | Write queries to insert sample data |
| 5.2.8 | Task | Test queries/database | 0.5 hour | 5.2.5 Verify successful data upload | Write queries for any updates that need to be made |
| 5.2.9 | Task | Debug and optimize database | 2 hours | 5.2.8 Test queries/database | Research best practices for adding/embedding databases into html website |
| 5.3 | Work Package | Integrate | 11 hours | -- | |
| 5.3.1 | Task | Research best practices for adding/embedding databases into html website | 4 hours | 5.2.8 Test queries/database | Debug and optimize database |
| 5.3.2 | Task | Write code to add to site | 4 hours | 5.3.1 Research best practices for adding/embedding databases into html website | |
| 5.3.3 | Task | Test site to ensure compatibility | 1 hour | 5.3.2 Write code to add to site | |
| 5.3.4 | Task | Troubleshoot errors and rewrite any necessary code | 2 hours | 5.3.3 Test site to ensure compatibility | |
| ▾ 6 | Deliverable | Business Analysis | 5 days, 6 hours | -- | |
| 6.1 | Work Package | Research | 21 hours | -- | |
| 6.1.1 | Task | Identify a Business to Analyze | 6 hours | -- | |
| 6.1.2 | Task | Identify their practices and areas for improvement | 12 hours | 6.1.1 Identify a Business to Analyze | |
| 6.1.3 | Task | Decide on relevant information and what to include | 3 hour | 6.1.2 Identify their practices and areas for improvement | |
| 6.2 | Work Package | Analysis | 4 days | -- | |
| 6.2.1 | Task | Use data to find important information/potential solutions. | 2 days | 6.1.3 Decide on relevant information and what to include | |
| 6.2.2 | Task | Create analysis/solutions. | 2 days | 6.2.1 Use data to find important information/potential solutions. | |
| 6.3 | Work Package | Present | 9 hours | -- | |
| 6.3.1 | Task | Create display method for presenting analysis to Business | 6 hours | 6.2.3 Use data to find important information/potential solutions. | |
| 6.3.2 | Task | Present to Business | 1 hour | 6.3.1 Create display method for presenting analysis to Business | |
| 6.3.3 | Task | Make any necessary adjustments. | 2 hours | 6.3.2 Present to Business |
💰 8. Budget
8. Budget
| Cost Item | Quantity/Hours | Rate/Price | Total Cost | Notes |
|---|---|---|---|---|
| LABOR COSTS | ||||
| Developer | 253 | $66.00 | $16,698.00 | ZipRecruiter |
| Graphic Designer | 460 | $28.00 | $12,880.00 | ZipRecruiter |
| Project Manager | 141 | $53.00 | $7,473.00 | ZipRecruiter |
| Tester | 3 | $41.00 | $123.00 | ZipRecruiter |
| Database Administrator | 144 | $53.00 | $7,632.00 | ZipRecruiter |
| Compliance Officer | 516 | $51.00 | $26,316.00 | ZipRecruiter |
| LABOR SUBTOTAL | 1517 | $71,122.00 | ||
| EQUIPMENT / SOFTWARE | ||||
| Software Licenses | 1 | $120.00 | $120.00 | Canva |
| Development Tools | 1 | $48.00 | $48.00 | GitHub |
| Testing Environment | 0 | $0.00 | $0.00 | |
| Database Software | 0 | $0.00 | $0.00 | |
| Other Equipment | 0 | $0.00 | $0.00 | |
| EQUIPMENT/SOFTWARE SUBTOTAL | $168.00 | |||
| MATERIALS | ||||
| Stock Images/Media | 0 | $0.00 | $0.00 | |
| Training Materials | 1 | $495.00 | $495.00 | ONLC Training |
| Certifications | 1 | $410.00 | $410.00 | Oracle Certification, Azure Certification |
| MATERIALS SUBTOTAL | $905.00 | |||
| SERVICES | ||||
| Cloud Hosting | 1 | $122.00 | $122.00 | Oracle APEX Pricing |
| Third-party APIs | 0 | $0.00 | $0.00 | |
| Consulting Services | 0 | $0.00 | $0.00 | |
| Security Audit | 0 | $0.00 | $0.00 | |
| Other Services | 0 | $0.00 | $0.00 | |
| SERVICES SUBTOTAL | $122.00 | |||
| SUBTOTAL DIRECT COSTS | $72,317.00 | Sum of all categories | ||
| Contingency Reserve (%) | 20% | $14,463.40 | Adjust percentage as needed | |
| TOTAL PROJECT BUDGET | $86,780.40 | Final budget amount | ||
| BUDGET BREAKDOWN | ||||
| Labor as % of Total | 98.35% | |||
| Equipment/Software as % of Total | 0.23% | |||
| Materials as % of Total | 1.25% | |||
| Services as % of Total | 0.17% | |||
| Contingency as % of Total | 20.00% | |||
| Three Major Budget Risks |
1. Increased work time can increase cost of labor 2. Increase in subscription-based price would increase software costs 3. Delayed timing would increase software costs since they are subscription-based |
|||
| Contingency Justification | I chose 20% as my contingency because my biggest cost is labor and I want to have space in my budget for labor overruns. Since my project is of low to moderate risk, 15–20% would be a good spot for a contingency budget. I like to be on the safe side, so I went with 20%. | |||
⚙️ 9. Project Methodology & Plan
Part 1: Assess Your Requirements
The requirements of my project are moderately clear with some uncertainty. I have some elements that have known requirements, while others are still in development and I am unsure what will be necessary to complete them.
Part 2: Determine Delivery Cadence
I will continuously deliver small tasks that will add to the final large delivery (the complete portfolio) at the end.
Part 3: Examine Each Approach
Predictive: Predictive planning could set motivating timelines, but it’s too rigid for a project with many changing factors, so it’s not a good fit.
Hybrid – Incremental: Incremental suits my project because I can add independent pieces over time, but it assumes the website is built first, which conflicts with my current plan.
Hybrid – Iterative: Iteration is valuable for design/about/website elements that need feedback from mentors and contacts; it’s less necessary for items like certificates.
Agile: Agile could work in theory, but the sprint pace and stakeholder involvement would be heavier than I want. I prefer longer cycles between feedback.
Part 4: Choose Your Methodology
I will use the Hybrid-Incremental approach.
- Allows flexibility in components of the project.
- Focuses on completing individual deliverables before moving on.
- Enables presenting completed pieces for feedback and making adjustments.
Part 5: Project Plan Diagram
I used Lucidchart to create my project plan diagram. It reflects my choice of hybrid incremental as it has many small steps that add up to the larger project. I start by working on the design of my website. After getting feedback, I will return to make adjustments, then use the somewhat finalized design to build when writing the HTML/CSS/JavaScript. This step will also go through a round of feedback and editing. Finally, I will adapt my website to ensure mobile responsiveness.
As for the other elements of my project (certificates, projects, and various content), these are less dependent on each other. I will complete these individual pieces throughout the semester and keep them ready to be added to the final portfolio once the website is complete.
Part 6: Tools
Tools Considered: Monday.com, Trello, and Microsoft Project
I chose to use Monday.com. It has a good level of functionality and allows tasks and deliverables to be seen in a more manageable format. Compared to others:
- Trello: Familiar, but becomes cluttered too easily.
- Microsoft Project: Structured but lacked freedom and features I liked in other tools.
- Monday.com: Can display a lot or a little of information depending on the selected view. Has many useful features to track details of each deliverable and task.
Monday.com has system features that make entering and altering data easy and efficient.
Part 7: Project Phases
Plan → research and quick feedback
Execute → longest phase with cycles of work and
feedback plus adjustments
Test → integrate content and verify site
behavior
Deliver →
submit the finished project.
