Management21 topics
IT project and product management
IT project management is the set of decisions that turn an intention into shipped software: what to build, how to cut it into work that can actually be finished, how the team runs itself week to week, and how the result reaches users. This section covers 21 topics in five groups — product management, decomposition, methodologies, the release process and the formal frameworks — and each page gives the trade-off behind the choice rather than a summary for a certification exam.
What is inside
Each area below is a group of topics. Open one to read its pages.
- Product ManagementDeciding what is worth building, and how you will know whether it worked.DiscoveryRoadmappingMetrics
- DecompositionCutting a large intention into pieces small enough to estimate, finish and check.WBSUser storiesOKR
- MethodologiesHow the team runs week to week — and honestly, where each method stops working.ScrumKanbanScaling
- Release ProcessGetting the work to users: branching, what a release actually promises, and rollback.BranchingFeature flagsChangelog
- FrameworksThe formal wrappers — governance, roles and stage gates around everything above.PMBOKPRINCE2
Where to start
- New to any of thisStart with Agile to get the vocabulary straight, then Scrum for the one framework most teams actually run.
- Your sprints keep slippingThe problem is usually decomposition rather than the method. Read User Stories, then Kanban for flow and WIP limits.
- Coordinating five or more teamsGo straight to the scaling comparison: SAFe for structure, LeSS for de-scaling, Nexus for the smallest step up from Scrum.
- Asked to run a formal projectPRINCE2 for the method and its stage gates; PMBOK for the body of knowledge behind most certifications.
Other sections
- DevelopmentSoftware development is the work of deciding where the boundaries in a system go, what runs on each side of them, and what moving one of those boundaries will cost once the code is live. This section covers 28 topics — architecture, the browser, five backend runtimes, four mobile platforms, language models and the databases underneath all of it. Every page turns on the constraint that actually separates the options, rather than on the API surface.
- QAQuality assurance is the practice of deciding what to check, running those checks often enough to be worth having, and knowing what changes when the thing under test stops giving the same answer twice. This section covers 9 topics in three groups: the types of testing everyone half-remembers, automation with Playwright, Cypress and Selenium, and testing products built on language models — where an assertion becomes a score rather than an equality.
Found this useful?
Share it with someone who is working on the same problem.