normanrs/ns_agile

## ns_agile
Norm Schultz
Reflections on Agile Workflow and Professional Feedback

What have you learned about the use of agile vs. waterfall in software projects?

Our instincts are geared toward following a waterfall-style workflow. It appears logical: examine the scope of a problem, carefully create a solution, and do it. But large projects tackled by a team do not lend themselves to this method. An agile approach represents setting fairly smal "packaged" goals and attaining them, giving you the ability to both learn along the way and pivot (with only small resource waste) as understanding and requirements change.

How did you and your group approach project management in this project (what tools did you use, how did you hold each other accountable, etc.)?

We used Waffle and created "flights" which were in-line with an agile approach. Each flight represented a "deliverable" working website and as flights progressed the site got closer and closer to completing the major objectives.

What role did you take on in the project?

I was the leader of the project, guiding the setting of flights and sub-tasks, getting feedback from everyone, checking on progress, and "floating" to help when needed.

What changes would you make to your approach in future team projects?

I think I would set "backup" deadlines: if someone was still working on a task past the original deadline other team-members automatically checked on them and helped them complete.

How does retro function in a team project?

It's a chance to discuss what went right and wrong so as to improve and makes sure everyone is OK to work together again in the future.

In your team retro, how did you engage in the feedback process? What principles of feedback did you use in these conversations?

We did not have a team retro - there doesn't seem to be time and it wasn't assigned.

How would you describe your ability to communicate feedback? How has this experience affected your communication skills? How do you want to improve in your ability to communicate feedback?

I feel like through these sorts of experiences I'm getting better at being able to motivate people without pissing them off. But at the same time I'm not sure these projects represent what would happen at a company or organization.
	Norm Schultz
	Reflections on Agile Workflow and Professional Feedback

	What have you learned about the use of agile vs. waterfall in software projects?

	Our instincts are geared toward following a waterfall-style workflow. It appears logical: examine the scope of a problem, carefully create a solution, and do it. But large projects tackled by a team do not lend themselves to this method. An agile approach represents setting fairly smal "packaged" goals and attaining them, giving you the ability to both learn along the way and pivot (with only small resource waste) as understanding and requirements change.

	How did you and your group approach project management in this project (what tools did you use, how did you hold each other accountable, etc.)?

	We used Waffle and created "flights" which were in-line with an agile approach. Each flight represented a "deliverable" working website and as flights progressed the site got closer and closer to completing the major objectives.

	What role did you take on in the project?

	I was the leader of the project, guiding the setting of flights and sub-tasks, getting feedback from everyone, checking on progress, and "floating" to help when needed.

	What changes would you make to your approach in future team projects?

	I think I would set "backup" deadlines: if someone was still working on a task past the original deadline other team-members automatically checked on them and helped them complete.

	How does retro function in a team project?

	It's a chance to discuss what went right and wrong so as to improve and makes sure everyone is OK to work together again in the future.

	In your team retro, how did you engage in the feedback process? What principles of feedback did you use in these conversations?

	We did not have a team retro - there doesn't seem to be time and it wasn't assigned.

	How would you describe your ability to communicate feedback? How has this experience affected your communication skills? How do you want to improve in your ability to communicate feedback?

	I feel like through these sorts of experiences I'm getting better at being able to motivate people without pissing them off. But at the same time I'm not sure these projects represent what would happen at a company or organization.