0

I am planning to create a full stack web app (Spring + ReactJS) with my friend to build my portfolio. I've created such apps before, so skills wise I'm good to go. But this time I want to do it in a structured way.

I want to use the "project management" method where I gather requirements, and from that, create a user story, use case diagram, then proceed to code, then test, then deploy (not in order here).

My question is: is there a template for me to follow?

I know "gather requirements" or "user story" or "agile" but I'm unsure on which one to do first. And I am not sure if there are other steps that I need to follow, which is a bit messy. Having a template allows me to do it properly, in order, so I don't miss anything. Something like SDLC.

Most of the tutorials on building apps focus on what the app is about and proceed to code, which is useful. But having the full project management thingy is the ultimate goal, kind of like doing the project for a client. Everything is documented and you show your client diff stages of the project with diff docs as you progress.

Hope my question makes sense.

2
  • 3
    There isn't one way to manage your project because that depends on the characteristics of your project. As a result, there isn't a template you can use, unless you already decided on which management approach to use. As your question reads, it seems that your goal is to learn project management, which is a very broad topic. If you have specific questions you might try to ask those instead. – Bogdan Jun 22 at 9:40
  • @Bogdan the issue is i dont know where to start and what to ask. perhaps a generic one? supposed i wanna do a to-do list app using Spring, Mysql and React, what is the common approach? all im asking is a sample or reference so i can slowly start from there – shalam mohsen Jun 25 at 2:10
1

Try to follow agile software development principles

It is now well established that following Agile Software Development principles results in more successful outcomes. The Agile Manifesto is here. Among the Agile processes, Scrum is the dominant software development framework. But, your team is too small to practice Scrum because you will be missing some key roles.

However, you can try to implement the Agile principles in the following ways:

  • Working software over comprehensive documentation: Put more focus on working software and do only absolutely essential documentation.
  • Deliver working software frequently: Run two week sprints and deliver fully tested, production ready software every two weeks.
  • Satisfy the customer through early and continuous delivery of valuable software: Demo the software to the customer at the end of each two weeks and get their feedback.
  • Welcome changing requirements, even late in development: Based on seeing the demo, if the customer wants to make some changes, accommodate them.
  • Continuous attention to technical excellence:
  1. Code review: You have a 2-person team. You can each review the code written by the other.
  2. Write unit tests: Unit tests help you to refactor code, when needed, without risk of breaking existing functionality.
  3. Write integration tests: Verify end-to-end functionality is not broken.
  4. Continuous integration: Run automated tests on each check-in so that issues are not discovered late in the cycle.
  • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly: Every two weeks review your process objectively and make improvements, as needed.
3
  • i have some ida about the stages 1-5 u described, but i think i need guidelines / references in the stages before this eg after gathering requirements, how do i set it in writing? business req -> func reg -> use case -> uml diagrams.. i wanna start code using a proper planning and diagrams. i am tired of coding just like that and ending up missing few key functions and having to refactor the whole code. hope you get where im getting at.... – shalam mohsen Jun 26 at 17:25
  • 1-5 are not stages. These are agile principles. There is no separate 'gathering requirements' stage in agile. You may want to go back and study the why, what and how of agile. – Ashok Ramachandran Jun 27 at 7:40
  • my question is regarding the steps / stages before this 'principles'. eg, business req -> func reg -> use case -> uml diagrams. if there a reference or template? – shalam mohsen Jun 28 at 11:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.