map


The collection of posts, loosely defines the overall process for product development. From understanding the problem from the User/Domain to a solution as a Feature, defined by Requirements. Sometimes I veer off and talk about technology and mathematics.

Market/problem definition

Customer


  • Personas and JTBD The customer/stakeholder Who and Why goals, success
  • What is the concept, how do they do it now?
  • Goals/assumptions/ strategic fit

Domain


  • Domain info and modelling - Domain problem statement
  • Problem statements to clarify solutions

Product definition

Context: market-product fit key problems
  • domain knowledge and subject matter expertise
  • User Flows/UX
    • design sprint/mock-ups/experience
https://jseller.blogspot.com/2019/12/the-w5-of-developing-software-products.html
https://jseller.blogspot.com/2019/09/building-technology-for-non-developer.html

Product design

Context: User scenarios/UX flows and domain rules/requirements
  • User story mapping 
    • UserStory / acceptance criteria (Given-When-Then)
    • linking requirements to acceptance
  • Themes, features and requirements
    • Usability, Security, Performance, Observe-ability, Maintain-ability
    • Feature flags and product versions/pricing
  • Requirements need to be versioned to the release for testing, while new requirements are defined for later versions.

Architecture 

Context: Requirements
  • Structure: 4Cs diagram: Context (link to requirement) , Containers, Components, Classes
  • Behavior: Dynamic or sequence diagrams
https://jseller.blogspot.com/2019/01/feature-definition-with-quality-model.html

Product implementation

  • epics and work items/issues
  • story mapping
    • scope of work, estimates
  • programming
  • closing issues
https://jseller.blogspot.com/2019/04/scaling-your-web-application-for-many.html
https://jseller.blogspot.com/2019/04/database-design-for-web-applications.html
https://jseller.blogspot.com/2016/01/lamp-development-on-windows.html

Programming

https://jseller.blogspot.com/2016/11/algorithms-intro-implementing-math-proof.html
https://jseller.blogspot.com/2016/11/algorithms-intro-profiling-python-code.html

Teamwork

https://jseller.blogspot.com/2019/01/conversational-software-development.html
https://jseller.blogspot.com/2019/01/undisciplined-refactoring-can-create.html
https://jseller.blogspot.com/2020/02/production-quality-code-tests-for-win.html

Product releasing

  • dev release notes and semver
  • acceptance and experience testing
  • operations deploy, monitor
  • product release to customers
https://jseller.blogspot.com/2019/01/software-releases-are-lot-more-than-code.html

Product operations

  • servicing outside requests
  • bugs, feature requests, problem strategy
    • add to product definition with feature requests, align problem to strategy
    • add to product design with bugs, align requirements 
https://jseller.blogspot.com/2017/03/projects-and-systems.html
https://jseller.blogspot.com/2019/01/scrum-xp-fdd-or-kanban-use-all-of-them.html

Technology

https://jseller.blogspot.com/2019/10/ai-can-help-if-trained-to-do-so.html

Math

https://jseller.blogspot.com/2015/08/dont-have-anxiety-about-math-its-nice.html
https://jseller.blogspot.com/2016/11/check-your-lotto-chances-what-do.html
https://jseller.blogspot.com/2016/11/checking-my-lottery-chances-with.html





No comments:

Post a Comment