Your browser is blocking local storage, so your progress will be lost when you close or reload this page.

How software teams communicate, work together and learn.

Topics

• Common Development TerminologyExpected level: Working

  Understand the expressions used daily in software teams (see Glossary).

  Not reviewed
• Effective Technical CommunicationExpected level: Proficient

  Explain technical concepts clearly, in writing and verbally.

  Not reviewed
• Asking Good QuestionsExpected level: Proficient

  Provide context, evidence, and attempted solutions.

  Not reviewed
• Documentation SkillsExpected level: Working

  Write information others can understand and maintain, including Markdown.

  Not reviewed
• Agile, Scrum, and KanbanExpected level: Working

  Understand iterative delivery and common work management approaches.

  Not reviewed
• Giving and Receiving FeedbackExpected level: Working

  Handle code review and peer feedback constructively.

  Not reviewed
• Knowledge SharingExpected level: Working

  Participate in reviews, demos, and technical discussions.

  Not reviewed
• Ownership and Time ManagementExpected level: Working

  Manage tasks, flag risks early, and follow work through to done.

  Not reviewed
• Continuous LearningExpected level: Working

  Learn new tools and concepts independently and efficiently.

  Not reviewed
• Estimation BasicsExpected level: Awareness

  Understand effort, uncertainty, and planning.

  Not reviewed

Self-assessment

You should be able to do each of these without help.

• Explain a user story, its acceptance criteria, and the team's Definition of Done. Use a story from your own team to show how the three differ.Related: Requirements and User Stories, Agile, Scrum, and Kanban, Ownership and Time Management
• Ask a question that includes context, evidence, and what has been tried. Someone should be able to answer it without coming back to you with follow-up questions.Related: Asking Good Questions
• Explain a technical topic to a non-technical colleague in a few sentences. Avoid jargon and use a familiar analogy or an example from their own work.Related: Effective Technical Communication
• Write a short status update about a problem. Lead with the conclusion and what you need, and keep what is confirmed apart from what you only suspect.Related: Effective Technical Communication
• Raise a risk early. State the facts, the impact, your options and when you will give the next update.Related: Ownership and Time Management
• Write a README that lets a colleague set up and run a project. Test it by following the steps yourself on a clean machine, or have someone else try.Related: Documentation Skills, Repository Structure
• Write up something you learned in five to ten lines with one example. Put it where the team will find it again.Related: Knowledge Sharing, Documentation Skills
• Explain ten glossary terms in your own words. Pick terms you have heard but never had to define, and check your explanation against the glossary.Related: Common Development Terminology