Date
Jul. 21st, 2024
 
2024年 6月 16日

Post: Dev cycle Cheatsheet

Dev cycle Cheatsheet

Published 08:08 Aug 02, 2020.

Created by @ezra. Categorized in #Programming, and tagged as #Cheatsheet.

Source format: Markdown

Table of Content

Software Development Life Cycle

  • [ ] Idea
  • [ ] Planning
  • [ ] Analysis
  • [ ] Design
  • [ ] Implementation
  • [ ] Testing and Integration
  • [ ] Documentation
  • [ ] Maintanance

Types of it are: - Agile (Scrum is the framework of it) -- Small incremental changes - Lean -- The Lean process is about working only on what must be worked on at the time, so there’s no room for multitasking. - Waterfall -- finish one phase, then move on to the next. No going back (oldest - baddest) - Iterative -- The Iterative model is repetition incarnate. Instead of starting with fully known requirements, project teams implement a set of software requirements, then test, evaluate and pinpoint further requirements. - Spiral - it is the same with iterative deisgn but for bigger projects with these steps (planning, risk analysis, engineering and evaluation) always minimize risk - DevOps -- In a DevOps model, Developers and Operations teams work together closely. Updates to products are small but frequent.

Scrum

This is just a cheatsheet for orginizing my scrum headers. It doesnt have to be on your project files you can orginze them in softwares such as trello or else but the setup below is efficent to use:

  • Product Backlog -- Add the main features for example while developing instagram.com you would add "home app", "profile", "search engine", "settings", "help center" ... etc. Add an explanation for its overview. You will break it down in the sprint backlog

  • Sprint Backlog -- In this part take the most important feature from "product backlog" and move it there. Break down the feature as much as you can. And prioritieze of the features pieces. While gluing them together.

  • In Progress -- Move the "sprint backlogs" that you are working on to here to avoid confusion. Again prioritize and if the sprint backklog is too huge, dont worry you can do a feature in two sprints too.

  • Quality Testing -- After finishing the progress move the feautres to be tested. If anything is not right fix it. And once they are done move it to the documentation section.

  • Documentation -- This is self explainatory. Once a feature is there document everything about it. Documentation is the most important insurance you can get.

  • Spring Review -- Well once a feature is here. First review everything. from product backlog, sprint backlog, progress, tests to documentation. If everything looks good than remember everything about agile is iteration, a feature is never done; so think about what will be in the next version of this feature and add the next version with an overview to its respective place in "procut backlog". So see youre starting again from the top. The hamster wheel never stops. And move the finished verison to "done". Note: the older versions that are remaining in the "product backlog list should be prioritized over the newly iterated version 2 product backlogs"

  • Blocked -- Move a "sprint backlog"s checkboxes and its "In progress" checkboxes to here if something is blocking that features development. Until it gets fixed and the block is removed that feature remains inside this little quarantine.

  • Done -- If a feature is here, it is done and ready to be shipped and merged to the main product.

Pinned Message
HOTODOGO
I'm looking for a SOFTWARE PROJECT DIRECTOR / SOFTWARE R&D DIRECTOR position in a fresh and dynamic company. I would like to gain the right experience and extend my skills while working in great teams and big projects.
Feel free to contact me.
For more information, please view online résumé or download PDF
本人正在寻求任职 软件项目经理 / 软件技术经理 岗位的机会, 希望加⼊某个新鲜⽽充满活⼒的公司。
如有意向请随时 与我联系
更多信息请 查阅在线简历下载 PDF