Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project plan #3

Open
markotaht opened this issue Sep 9, 2015 · 0 comments
Open

Project plan #3

markotaht opened this issue Sep 9, 2015 · 0 comments
Milestone

Comments

@markotaht
Copy link
Owner

Roles in project. You have understood each team member roles and assigned responsibilities.
Communication means. You have agreed both among yourselves and with the customer how and when and via which channels you are going to communicate.
Work process. You have understood how you are going to work together and have explained this to me. I understand at minimum:
    How and using what materials the customer is going to understand what you are going to build
    How do you determine that the customer is accepting your solution proposal
    How you are internally going to build the accepted solution (who assigns the tasks, who is going to implement it, will the tests be written, will code be reviewed, who is going to verify, who is doing the validation, etc)
    When do you consider something ready to be published to the customer for review
    How do you gather feedback from the customer and/or end users.
    What is the definition of DONE on a task 
Scope. You have created the list of all tasks you currently foresee need to be delivered in order to complete the project. Tasks are planned into iterations or given priorities, assigned to person responsible and contain initial estimation about the amount of work involved. The descriptions of the tasks in the project plan is understandable.
    At least tasks deliverable during the second iterations must be detailed in project plan. Further iterations might not be clear enough to break them down to tasks according to your current knowledge about requirements.
    The tasks in the second iteration are defined at the proper level of granularity (90% of tasks take less than 16 hours, no task is larger than 40 hours). 
@markotaht markotaht added this to the 1st iteration milestone Sep 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant