Computer Science Project Development with a Team is a genuinely professional-simulation course — presenting real technical work to a mock leadership team, complete with peer review.
What D687 covers
Students prepare a prior project for submission to a mock technical and executive leadership team, expanding on prior coding work by submitting three artifacts: an executive summary of product requirements, a technical report of the functional data product, and a business proposal aimed at convincing stakeholders to implement the project.
Artifacts are evaluated by peer team members before submission, and students practice giving, receiving, and integrating feedback.
The D687 performance assessment
Expect a performance assessment requiring all three artifacts — executive summary, technical report, and business proposal — for a prior coding project, incorporating peer feedback before submission.
Key topics in D687
- Executive summary writing for a technical audience
- Technical reporting on a data product
- Business proposal development
- Peer review and feedback integration
Writing tips for D687
Follow the task instructions and rubric line by line
WGU performance assessments for D687 are graded against a fixed rubric — every rubric line has to be visibly addressed, usually with a labeled heading that mirrors the rubric language. Skipping a rubric point because it seems minor is the single most common reason a competent submission comes back "Not Yet Competent" for revision.
Show your work: code, reasoning, and test results, not just a final answer
WGU evaluators are trained to distinguish genuine technical work from a paraphrased summary. Include your actual code, algorithmic reasoning, and test/benchmark results, not just a description of what you built — a rubric checking technical competency wants to see the artifact and the thinking behind it.
Because WGU is self-paced, don't let "no deadline pressure" become no submission
There's no weekly due date forcing progress, which means procrastination costs more at WGU than at a traditional term-based school — a stalled task can quietly eat weeks of a term. Treat your own target date for each D687 assessment as a real deadline.
Stuck on your D687 task?
Our writers know WGU's competency-based format and this course's performance assessment. Get an original, properly cited paper matched to your task instructions.
Why students seek help with D687
Students sometimes submit only the technical report and treat the executive summary and business proposal as afterthoughts — all three artifacts are explicitly required and each targets a genuinely different audience and purpose.
How GradeEssays helps with D687
Share your prior project and rubric, and your writer will build all three artifacts — executive summary, technical report, and business proposal — each properly targeted to its intended audience.
Get Help With D687
Share your task instructions and rubric and we match you with a writer who knows this course and WGU's evaluation standards.
Place Your Order View All ServicesPrerequisites and program context
D687 builds on a prior coding project from earlier CS coursework.
- Bachelor of Science, Computer Science
- Bachelor of Science, Computer Science (BSCS to MSCS)