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,...
-
Have you ever created an app before, either for Android or iPhone? How did it go? Do you have any ideas for apps that you could create ...
-
This week, we learned about debugging techniques. There are multiple ways to do this such as glass-box, black-box, testing edge conditions, ...
-
Microservices Microservices are used by companies to make their code more reusable by allowing engineers to combine ready made parts i...
No comments:
Post a Comment