over 1 year

Now Change Future

Tech Project Success For Internet-First Organizations

The Internet Everywhere World

The modern organization, whether business, government, or community has to evolve or die in an internet-dominated environment.

Software engineering is eating the organizations world.

To protect and expand its mission, the organization must embrace the challenges of an internet-everything reality, and own the internet-centric software development process through efficient, pragmatic, and effective use of people, technology, and time.

Now Change Future

Now, Change, Future
  • 1: Now: current state of system/thing
  • 3: Change: what energy, time, information is required to work the change of state
  • 2: Future: future state of the system

Project Frameworks

There is a spectrum of formal project management frameworks from lean methods to more formal and intensive.

  • Kanban: uses a columned board and suits bug fixes and continuous improvement. Breaks down with larger teams and task lists.
  • Scrum: a weekly or biweekly cicyle of team planning, daily scrum meetings (standups), sprint review/demo and sprint retro.
  • SAFe Scaled Agile Framework Enterprise: there are four configurations available for large organizations to implement scaled agile, Essential SAFe, Large Solution SAFe, Portfolio SAFe, and Full SAFe.
  • PMBOK: The Product Management Body of Knowledge is a very formal and heavy method that is used by large, formal organizations such as government or engineering corporations.
  • Six Sigma: is a formal and structured project management framework used to continuously improve especially in manufacturing.


Scrum is a popular lean Agile framework that encourages a regular cadence of teamwork and collaborative problem-solving. Even if the organization chooses a formal company framework, culture and people will implement their own flavor or hybrid.

Miro has a good article describing the differences between Kanban and Sprint. https://miro.com/blog/scrum-kanban-boards-differences/

  1. Product Backlog: product owners & managers create the product backlog list of features, requirements, improvements, and bugs. The product backlog is input or the source for the sprint backlog. The product backlog is constantly curated and maintained by product owners to match a dynamic market or environment.
  2. Sprint Backlog: work items such as stories or bugs are selected by the scrum dev team in this sprint cycle.
  3. Sprint Goal: is the incremental output of the work done during the sprint and should be a tangible and concrete output.

Cross Functional Technical Program Management in a Modern Organization

  • Software Eats the World
  • Start Small and Grow Organically With the Company
  • Executives and Management want to see roadmaps and Gannt charts
  • Product Developers want to see agile iterative processes

Business Documents

Documentation is key to communicating and organizing. Examples include;

  1. Business Documents / Artifacts
  2. Product Specs
  3. Customer Experience Design
  4. Service Design
  5. Customer Journey Mapping
  6. Project Management Systems
  7. Project Management elements
  8. Epics, Stories, Tasks, Subtasks, Bugs, Feature Requests
  9. Every element is assigned an owner for each project

Technical Project Manager

A cross-functional technical project manager must always adapt to the Current Situation.

Business Functions

  1. What existing business functions?
  2. Probability
  3. Product
  4. Software Engineering
  5. Systems (SOC)
  6. Networking (NOC)
  7. Security
  8. IT
  9. Logistics
  10. Facilities
  11. Design
  12. Marketing
  13. Advertising
  14. Support Tiers
  15. Sales
  16. Documentation
  17. HR


Culture can be explored by the following questions; 1. What are the existing project management processes, cultures, or historical norms? Different projects styles/formats/approaches

Maturity Project Culture

Project Management "Office" becomes the Program Management Office. Individuals working on isolated tasks merge organically into team-based projects which are organized thematically and coordinated into synergistic projects of projects called programs. Avoiding the Project manager as a professional nag by using Google's methods OKR.


  1. Boards
  2. Standups
  3. Shared Language
  4. System Diagrams
  5. Change Management
  6. Change Log
  7. Product Roadmaps
  8. Kanban boards
  9. Scrum boards
  10. Gannt charts
  11. Product specifications
  12. Project work breakdown/"task list" i.e. Epics, Stories, Tasks, Sub-tasks etc Project Progress
  13. Individual Contributor worklists
  14. Project Dashboards
  15. Program Dashboards
  16. Project Charters
  17. Motivations: OKR, KPI, performance metrics, delivery, outcomes
  18. Project Success
  19. Definition of Done

Project Management and Product Management

  1. Project managers focus on how and when
  2. Product managers focus on what and why
Sometimes project managers do product management and product managers do project management without the formal title. > Before product management became popular, good cross-functional project managers did product management. Nowadays, technical project managers work in coordination and in service to product managers.