What is ISP/ISMP?
ISP (information strategy planning) and ISMP (information system master plan), told as a story about mapping out what a publishing house will put out ahead of time.
The editor starts books on whatever's at hand.Nobody knows what should come out first.
Chasing only bestsellers loses the house's overall direction.Chasing trends alone loses the house's own identity.
ISP draws the big picture of what to publish and in what order; ISMP details how to build one series.ISP/ISMP comes before audit — it's the plan itself.
The roadmap is drawn by looking at four things: readers, rivals, capability, and priority.ISP covers the whole house; ISMP details how to build one specific series.
The roadmap doesn't write the book for you.The roadmap is a map that sets direction, not the manuscript itself.
ISP = a big-picture roadmap drawn ahead of time, deciding what to publish and in what order. ISMP = a plan drawn ahead of time, detailing how to build one series.
ISP (Information Strategy Planning) sets an organization's information direction and priorities in line with its business strategy, while ISMP (Information System Master Plan) targets one specific system and pins down the functions and requirements it needs. ISP works at the whole-organization level and ISMP at the level of one system, and both come before the build project begins.
When grown-ups say it
- ISP
- Setting the direction for the whole house. Lines up IT priorities with business strategy.
- ISMP
- A detailed plan for building one specific series. It can follow ISP, or stand alone depending on the organization.
- IS Audit/PMO
- The checker who watches the whole publishing run. Audit comes after ISP/ISMP, once the build project is running. A PMO can start as early as the planning stage. →the checker who watches the whole publishing run
- Requirements Engineering
- Taking down one book's own outline precisely. Happens for a single book, after the roadmap is set.
- BPR
- Overhauling the publishing process itself. Often discussed alongside ISP at the organizational level.
- Architecture Principles
- The shared style guide every book must follow. A rule to follow while carrying out the roadmap.
- Resource Allocation
- Deciding which writer goes on which book. Gets more specific as the plan gets more detailed.
- Feasibility Study
- Checking in advance whether the book can really be made. Weighed while the roadmap is being drawn.