The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Edited, proofread, formatted, and published Software Development Life Cycle Methodologies for Information Systems: Modern Approaches, Governance, and Practice, Part I by Mohammad Ikbal Hossain, the foundational volume covering SDLC concepts and the major development methodologies, from Waterfall to Agile. Managed the project from manuscript to a live Amazon paperback, keeping the technical content clear, consistent, and ready for professional and academic readers.
The work, explained
This is the opening volume of a two-part technical series, so it had to establish the groundwork the rest of the series builds on. The first four chapters explain what SDLC means, why it still matters, and how it connects to project management, governance, risk, and requirements engineering. The next four examine specific methodologies, including Waterfall, the V-Model, Incremental, Iterative, Spiral, Agile, Scrum, Kanban, Lean, Extreme Programming, and Hybrid models. My editing focused on clear explanations, a logical progression from concept to method, and consistent use of technical terms across all eight chapters. A proofreading pass followed to catch grammar, spelling, and punctuation errors. I then formatted the interior as a clean, print-ready paperback, and finished by creating the Amazon listing with its description and metadata and releasing the book.
The work, in bullets
Editing: Improved clarity, structure, and flow across a technically dense, eight-chapter manuscript
Terminology consistency: Kept methodology names and technical terms uniform throughout (Waterfall, V-Model, Scrum, Kanban, and others)
Tone preservation: Maintained the author’s professional, instructional voice
Proofreading: Final check for grammar, spelling, punctuation, and typos
Formatting: Print-ready paperback interior suited to a professional reference title
Series consistency: Matched the look and layout of Part II, so the two volumes read as one series
Publishing: Created the Amazon listing, including description and metadata
Delivery: Managed the project end to end, from raw manuscript to a live, purchasable book
Book details
Title: Software Development Life Cycle Methodologies for Information Systems: Modern Approaches, Governance, and Practice, Part I
Author: Mohammad Ikbal Hossain
Editor: Fizza Belle
Format: Paperback
Series: Part 1 of 2
Chapters 1 to 4: Foundations of SDLC, its role in the digital era, its link to project management, and how information systems projects create business value through scope control, stakeholder involvement, governance, risk management, and requirements engineering
Chapters 5 to 8: Structured models (Waterfall, V-Model), learning-based models (Incremental, Iterative, Spiral), and adaptive approaches (Agile, Scrum, Kanban, Lean, Extreme Programming, Hybrid)
Platform: Amazon
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Ramen Brand Identity
Oishii is a self-initiated branding project exploring the visual identity of a modern ramen brand. The concept combines Japanese-inspired aesthetics with a contemporary visual approach, creating a distinctive and cohesive identity across brand applications.
The project explores visual direction, typography, colour, and brand elements to build a memorable identity for a food brand.
Love the mix of Japanese-inspired style and modern branding. The identity feels cohesive and memorable.
On pretty much every introductory call where I show my design systems work in Figma and Claude, people get fascinated by my Figma/Claude files, Storybook setup, docs and guides—and how I make decisions so both humans and AI can pick these systems up.
I build these to help products scale at the pace they want, in the way they want, without having to fit everything around how the packaged or templatized headless libraries behave and function.
We also cover what both humans + agents absolutely must do when working together to ship: avoid long-term technical debt, save tokens as we ship fast, and keep production code as lean as possible.
One thing people really, really like is how I define and deal with what I call anti-patterns, account for edge cases, and put together a handoff-ready checklist for both design and engineering before shipping to production code.
Which combinations of components shouldn’t we use in bigger molecular patterns? What can’t we do? Can we define the edge cases and use cases where we shouldn’t use this component and should use another one instead?
This is so much more UX-led and rooted in systems thinking than UI-led.
If engineers are going to work with LLMs to churn out screens for you or your clients at speed, these rules and scenarios need to be part of the system. You need to run them through the LLMs too.
And here’s one very funny thing: this is extremely domain-led. You need to understand what to build, how to build it, and where it could go wrong. Claude or Astra can help you think through it, but you still have to test it with users. Not synthetic users, but real humans. And you better build the system in a way your design and engineering teams will actually use.
I think this is where so much of the edge lies: knowing what shouldn’t work, finding out what actually doesn’t, and making those decisions part of the system.
making docs readable for both humans and ai is the bit most teams skip. do you write the guides before or after the components?
Hole Story, a bagel brand concept with a pun you can’t unsee. Lilac backdrop, flying bagels and visuals good enough to eat.
Amazing
