Menu
Am wondering, when a new project arrives, say building a social networking website, how do I go about breaking the project into small tasks. There are usually 2-4 programmers per project and usually no testers as such. Should I be breaking the whole site into 4 hour tasks from the beginning itself. Should we be doing it in phases? What about testing, is it okay to have the programmers test the code?
Thank you for your time.
625
So, put simply, breaking a larger project down into smaller to-dos helps us easily identify what step we should take next. There's one more important note to make about this: This process shouldn't happen mentally (because, in case you already forgot, your memory isn't all that great).
Breaking down tasks into smaller and manageable units, makes the inter relationship between those units clearer, effectively helps the planning process, easier to revise and update plans when needed, assign work packages to appropriate skill groups, which makes it easier for the project manager to macro manage the ...
We use a fairly simple system.
We normally do this for each sprint for the activities that are to be completed within the sprint.
On testing programmers should test code by writing unit tests, but testers should perform the system test.
109
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
