Site Development Roadmap

Important

One step at a time.

Let’s cross that bridge when we come to it.

TODO: ## LeSS Explained Release

Engineering Practices & Tools Release ←

Target

  • Introduce some engineering practices to better adopt agile development.

Scope

  • Introduce engineering practices including User Story, Story Mapping, CI/CD, TDD, Pair Programming.
  • Demonstrate with examples and tools such as Github Actions, CircleCI, etc.

Task Breakdown

  • Create User Story page.
  • Create Story Mapping page.
  • Create CI/CD page.
  • Create TDD page.
  • Create Pair Programming page.
  • Update Roadmap page.

Scaled Agile Explained Release →

Target

  • Provide a high-level introduction to Scaled Agile, especially focusing on Nexus.

Scope

  • Explain Scaled Agile from a high-level perspective, stating the common problems.
  • Introduce Nexus framework.

Task Breakdown

  • Create Scaled Agile page.
  • Create Nexus page.
  • Update Roeadmap Page.

High-Level Scrum Explained Release →

Target

  • Provide a high-level introduction to Scrum.

Scope

  • Explain Agile Software Development from a high-level perspective, preferably with a diagram.
  • Explain the Values of Agile Software Development.
  • Introduce Scrum certifications, emphasizing that ‘knowledge does not equal understanding’.

Task Breakdown

  • Create Agile Development Page.
  • Create Scrum Page.
    • Create Scrum Certification Sub-Page Section.
  • Customize footer, logo, etc. on site to remove confusion.
  • Update Roadmap Page.

Vision Explained Release →

Target

  • Present the vision of the site.

Scope

  • Introduce Scrum and Agile Software Development.
  • Demonstrate how to build the site using a ‘small-to-big’ approach.

Task Breakdown

  • Implement the Vision page
  • Implement the site sidebar menu
  • Research and implement the multiple historical versions of the site
  • Customization of logo and footer
The Story behind the Scenes

Why implement the multiple/historical version functionality of the site?

  • Providing historical versions of the site for comparison will make the small-to-big approach intuitive and easy to understand.

Why the customization task is dropped?

  • During the development, I realized that elements like the logo and footer are not a top priority at this stage. Since the task can be completed before promoting the site, I decided to drop it in order to expedite the release.

Initial Release →

Target

  • Present the most important information about Scrum.

Scope

  • Get the site up and running.
  • Provide links to the most valuable sites and resources introducing Scrum and Agile.

Task Breakdown

  • Purchase Domain
  • Apply for SSL Certificate
  • Purchase VPS or Web Hosting Service
  • Basic Research on Web Implementation
  • Set up GitHub Repository
  • Create Home Page
  • Update Nginx Configuration to publish on Internet
  • Implement GitHub Actions Workflow for CI/CD
  • Research and Implement Full Text Search
The Story behind the Scenes

Why simply provide links in the initial release?

  • In the init release, listing those links delivers the most valuable information with minimal effort.

Why is the last task strikethrough?

  • When breaking down the tasks in the first place, I believed Full Text Search was an important functionality. People need it to search against the site for quick reference. However, I later realized that in the initial stage, the site contained very limited information, so the functionality didn’t make much sense. In addition, the Hugo Relearn Theme implements Full Text Search, meaning one less thing to worry about. Thank you Relearn Theme Contributors

How did you design the site’s technical architecture?

  • I leveraged AI to assist in analyzing the tech design. In addition, I understood that I would need to invest time and resources to experiment with and refine both the design and implementation.

Any difficulties in the init release?

  • Going from zero to one is always the most challenging part of building a product. Things like purchasing domain, applying for SSL certificate, etc. are relatively easy, because you can get the feedback and adapt to it quickly. However building the site itself, especially for the init release was not that easy.
  • The ‘real’ initial release was originally built using the excellent Grav CMS, and it worked pretty well until later I realized below requirements, which ultimately led me to switch to Hugo SSG.
    • I’d like to provide ‘historical’ version/release of the entire site and I need it to be done easily.
    • The site should be built with static elements as much as possible for better CDN delivery.
    • Maintaining a PHP server requires significantly more effort compared to using a static web server.
  • As a result, I migrated the site from Grav to Hugo during the initial release itself. I made the adaptation as early as possible to prevent further deviation and minimize technical debt.