What is the difference between implementation and realization in Mythical Man Month?
In Fred Brook’s Mythical Man Month chapter 4 (Aristocracy, Democracy, and System Design) page 49, he says:
Increasing User Changes/Requirements in Agile Methodology
My question is quite simple. How to handle a situation where the team is applying agile methodology in software projects and there so many iterations and change in requirements, that the schedule is highly affected? Plus you have your manager who is always wanting things to get done within schedule and it is something you cannot control?
Sourcecode license: free for personal use and modification but no public distibution
For one of my apps, I want to make the source code “open source” so that others might adapt the code to their personal needs or even contribute improvements, but I don’t want anybody else to publish “my app”. Furthermore, I still want to be able to sell the app at some time in the future.
Tex and Absence of bugs [duplicate]
This question already has answers here: Is it possible to reach absolute zero bug state for large scale software? (15 answers) Closed 11 years ago. I have been reading a lot lately and I have come across articles in which people make the ‘grand’ assertions that there are no bugs in the Tex program by […]
What are some ramifications of open source software turning into closed source software?
If a company takes a permissively licensed open source application and then develops a closed source application from that by reworking extensive parts of the application, adding new features and applying bug fixes…
What are some ramifications of open source software turning into closed source software?
If a company takes a permissively licensed open source application and then develops a closed source application from that by reworking extensive parts of the application, adding new features and applying bug fixes…
Solving which bugs will give greatest cost benefit
I wanted to get an idea of categorizing bugs based on how easy is it to solve and how much benefit it will give me. for e.g., if there is a bug which will take say an hour (double file close etc.) to solve vs another which takes a day (segmentation fault). But if solving the first bug is not very important, then I’ll probably work on the second one.
Solving which bugs will give greatest cost benefit
I wanted to get an idea of categorizing bugs based on how easy is it to solve and how much benefit it will give me. for e.g., if there is a bug which will take say an hour (double file close etc.) to solve vs another which takes a day (segmentation fault). But if solving the first bug is not very important, then I’ll probably work on the second one.
Solving which bugs will give greatest cost benefit
I wanted to get an idea of categorizing bugs based on how easy is it to solve and how much benefit it will give me. for e.g., if there is a bug which will take say an hour (double file close etc.) to solve vs another which takes a day (segmentation fault). But if solving the first bug is not very important, then I’ll probably work on the second one.
Solving which bugs will give greatest cost benefit
I wanted to get an idea of categorizing bugs based on how easy is it to solve and how much benefit it will give me. for e.g., if there is a bug which will take say an hour (double file close etc.) to solve vs another which takes a day (segmentation fault). But if solving the first bug is not very important, then I’ll probably work on the second one.