UPI Study › Courses › Project Management › Free lessons › Lesson 5.3 Free with a free account
Systems Development Tools and Project Management Software
Project Management · Chapter 5: Project Management Tools and Analytical TechniquesSection 5.3 · lesson 32 of 7312 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of Project Management.
Lesson complete
Earn the 3 college credits for Project Management
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: Henry Gantt's Legacy: Gantt Charts and Bar Graphs →← Precedence Diagram Method and Critical Success FactorsNext lesson: Henry Gantt's Legacy: Gantt Charts and Bar Graphs →
In this lesson
Matching project software to the life cycle, the team, and the work.
- Explain how sequential, iterative, and agile life cycle models shape which tools a project needs
- Describe requirements capture, prototyping, issue tracking, version control, scheduling, collaborative, and board-based tools
- Evaluate candidate tools with weighted criteria, must-have gates, and trials on real data
- Identify adoption pitfalls such as over-tooling, inconsistent use, missing owners, and late entries
Free study notes
Get this lesson's notes by email
The key points and 4 practice questions with answers, in your inbox. One email, free.
One email. Unsubscribe in one click.
Transcript
Everything said in the video, section by section (1,616 words). Read along, or search it.
Opening Question
Three Spreadsheets and a Double Order
Priya is a project office analyst at Millrace Bakeries, a regional chain of eleven shops. Her four-person team plans new shop openings with three emailed spreadsheets: tasks, equipment orders, and opening dates. Twice, two people edited different copies, and an equipment order was placed twice. Now she must recommend software. Should she pick the tool with the most features, or something else?
Core Idea
Tool Choice Follows the Work
Start with what a tool is: any software, or structured template, that records, calculates or shares project information. Tools fall into categories, defined by the project question they help answer, not by brand or screen layout. The central idea is that tool choice follows the work. The project's life cycle model decides which tools are useful, and so does its context: team size, location, outside access, and the rules that apply. And a tool doesn't fix a weak plan. A vague scope sits in tidy columns, and guessed estimates turn into precise-looking dates.
Life Cycle Models
Sequential, Iterative, and Agile Needs
A system is any mix of people, procedures and technology built to do a job. Its development life cycle runs from idea to retirement. Three models organize those stages, and they differ in what they assume about requirements, the needs the finished system must meet. The sequential model finishes each stage before the next. It assumes requirements are known early, and stay stable. So it needs requirements recorded early, a detailed schedule as a reference, and formal change records. The iterative model repeats design, build and review. It assumes requirements become clear as people react to working versions. So it needs ways to show people something early, keep versions under control, and log what each review found. The agile model delivers small, usable increments in short time boxes, and re-orders the backlog after each one. It assumes requirements keep changing. So it needs a shared, visible list of work that's easy to re-order, and little long-range scheduling. Which model is better is contested. Partly it depends on how stable requirements really are, and partly on how much certainty a sponsor may demand. This lesson takes no side.
Requirements Capture
Traceability Exposes a Louder Kiosk Tone
Now the categories. A requirements capture tool records each requirement as a separate numbered item, with its source, owner, priority, test, status and history. Its key feature is traceability: following a requirement forward to the deliverable and test that satisfy it, and any deliverable back to its requirement. At the Linden Reach Library, requirement R-12 says the new self-service kiosk must read a member card within a stated time. It links to the card reader, and to test T-12. Then Ade, a staff member, asks for a louder confirmation tone. No requirement connects to that request. So the team sees at once that it's a new request to assess, not a detail to slip in. That's how scope creep, uncontrolled growth in what's expected, becomes visible.
Prototypes
Low Fidelity Versus High Fidelity
At one of the shops, Priya shows Lena, the shop manager, a paper sketch of a new ordering screen. A prototype is an early, partial model of a deliverable, so people can react before the real thing exists. Even cardboard counts. A low-fidelity prototype is rough and cheap, like a paper sketch, or a wireframe. Because it looks unfinished, people criticize its structure: the order of steps, or a missing function. A high-fidelity prototype looks and behaves much like the real thing. It draws comments on wording, timing and ease of use, and shows whether someone can finish a task unaided. The price: a polished model costs more to change, and may be mistaken for nearly finished.
Issues and Versions
Trackers, Version Control, and Audit Trails
Back at the office, Owen asks how the team would stop another double order. An issue is a recorded problem, question, fault or request. An issue tracker stores each one with a reporter, an owner, a severity and a status, from open to closed. A version is one saved state of a file. Version control stores every version with who saved it, when and why, and lets the team compare, restore and combine work. Both keep a history, but the tracker stores the conversation about the work, while version control stores the work itself. Together they form an audit trail: each entry tied to a person, and never quietly rewritten. A shared team login defeats it, and so does using it to assign blame.
Work Organizing Tools
Scheduling, Collaborative, and Board-Based Tools
Three more categories organize the work itself. Classify the feature, not the package, since one product can mix several. A scheduling tool records activities, durations, links and calendars, and calculates the timeline. It's best at showing what a change does to the finish date. It struggles when the work is small or changes daily, and it can show dates more precisely than the estimates deserve. A collaborative work management tool is a shared workspace of tasks, owners, due dates, discussion and files. It's best at visibility for teams in different places. But its dependency logic is thin, so a late task's effect on later dates usually isn't calculated. A board-based tool shows work items as cards moving across columns of stages. It's best at showing what's under way, and what's stuck, but it carries little date logic.
Scheduling Software
Correct Arithmetic for an Impossible Plan
Scheduling software automates the arithmetic you've done by hand: the links, the forward and backward passes, and the critical path, on a working calendar. It can flag a circular chain, and it recalculates in moments when something changes, which makes what-if questions practical. What it can't do is judge whether the logic is right. At the Fenwick Community Hall, painting is scheduled to start the moment plastering finishes. Nobody entered the drying time. The software calculates a clean critical path, arithmetically correct, for a plan that's physically impossible. A neat output isn't evidence of a sound plan. Walk each link with the people who'll do the work, and ask whether the next step truly can't start until this one ends.
Quick Check
Seeing a Supplier Delay's Effect
Quick check. A planner links nine tasks, and wants to see how a three-day supplier delay would push the handover date. Which kind of tool fits best? Pause, and decide. A scheduling tool. It holds the links and calendars, and recalculates the dates when one task slips. A board-based tool shows where each task stands, and a collaborative workspace usually doesn't calculate the knock-on effect.
Selection Criteria
Six Criteria Weighted Before Any Demo
Choosing a tool takes six criteria. First, fit to the work: the model, the scale, and the questions the project really has, not the longest feature list. Integration: can it exchange data with tools already in use, so nobody types the same figures twice? Access control: can it limit who may see, and who may change, which information? Cost over time: the total cost of ownership across the tool's life, including set-up, training, administration and moving data, not just the first invoice. Support and training: is help available, and can the team learn it in time? And data portability: can the data be exported, so the team isn't locked in? To compare candidates, agree a weight for each criterion before looking at any tool. Score each one on real evidence, like a trial with your own data. And treat any must-have as a pass-or-fail gate, which strength elsewhere can't buy back.
Adoption Pitfalls
Over-Tooling, Inconsistent Use, and No Owner
Even a well-chosen tool can fail at adoption, the extent to which people actually use it as intended. Over-tooling means adopting more tools or features than the work needs, so effort goes into feeding them. Start small, and add a tool only when a real question needs it. Inconsistent use means people fill in fields and statuses differently, or two tools hold conflicting task lists. Write short conventions, and name a single source of truth. With no owner, nobody looks after set-up, access, clean-up and training, so the tool decays. Name an owner and a deputy, and give them time for it. Late or missing entries make the tool show the past. People stop trusting it, and keep private lists. Build entry into routines you already have, like the weekly meeting. A pilot, a small group using the tool on real work first, exposes most of these cheaply. How much tooling is right is itself debated, and no side is taken here.
Back to Millrace
Choosing the Tool the Team Will Use
Back to Priya. She found two candidates: a feature-rich scheduling tool, and a collaborative work management tool with a board view. Her constraint was the team's capacity, not money. Before any trial, she and Owen agreed the weights, with portability and access control as must-haves. In a one-week trial on the team's real task list, everyone entered their work in the second tool within an afternoon, and shop managers got view-only access. In the first tool, only Priya could enter the logic correctly. She'd have become the owner of everything by default. She recommended the second tool, and gave up automatic critical path calculation. An opening's truly dependent chain is short enough to check by hand, with a dated milestone list. She named Owen's deputy as the tool's owner, wrote one page of conventions, confirmed the data could be exported, and set a review after two openings.
Quick Check
Locked In After a Price Rise
Quick check. Two years in, a vendor doubles its price, and the team finds it cannot take its task history to another product. Which selection criterion exposes the problem? Pause, and decide. Data portability. With no way to export the data, the team is locked in, and a price rise leaves no real choice. Access control is about who may see or change information, and support and training about learning the tool.
Key Takeaways
Fit, Categories, Weights, and Adoption
To recap. Tool choice follows the work: the life cycle model, and the context. Each category answers one project question, so classify the feature, not the package. Agree weights before seeing candidates, and test on real data. And adoption needs an owner, written conventions, and entry built into routines the team already has.
About Project Management at UPI Study
Project Management (Business 230) is a self-paced online course of 73 video lessons in 12 chapters, from starting and defining a project to planning, budgets, scheduling tools, proposals, contracts, execution, monitoring, closure, teams and certification. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus All Business courses Every course with PRO →
Why take it here
Why students take Project Management with UPI Study
Where the credit goes
Universities that work with NCCRS
Project Management carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About Systems Development Tools and Project Management Software
What is requirements traceability in project management?
What is the difference between a low-fidelity and a high-fidelity prototype?
What is the difference between scheduling tools, collaborative work management tools, and board-based tools?
How should a team choose project management software?
About the Project Management course
How many college credits is Project Management?
How much does Project Management cost and what is included?
Which universities accept UPI Study credits?
How long does Project Management take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Project Management.
73 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →