This week, our group discussed the effective meetings reading from last week. It seemed like we already used a few ideas in the article through our CS learning. A number of meetings could have been done over email and didn't need to be discussed. Meetings are nice to have in general, just so everyone can get their input in all at once. We used to keep minutes but every big decision was later posted to the Hangouts chat to remind everyone later. It was concluded that this article was not software development specific because as we have read about, failure in software will happen. Deadlines can be missed and features could be implemented incorrectly, it is not unacceptable for this to occur. Features that take longer than expected is built into Agile's point design. I haven't worked in a professional software development setting, so I will have to see for myself if the tips in the article work.
Subscribe to:
Post Comments (Atom)
cst 499 week 8
This week, we finished writing the paper in order to do the best job possible even if it was a little bit late. Now that everything is done,...
-
o Part One: Set Your Educational Goals o I want to gain skills that are useful in the current industry. I want to be able to build...
-
Part I: Visit Time Management and Study Strategy Outlining Textbooks is an area of improvement I need to work on. A note taking te...
-
· Part One: Support and Comment on Teammates' Goals (30 min) o Visit at least two of your team members' blogs on edu...
No comments:
Post a Comment