Software Development - gusenov/kb GitHub Wiki
- The ReadME Project is part of GitHub's ongoing effort to amplify the voices of the developer community.
- Карта сайта проекта RSDN
- DOU Developers Community
- Делай как в Google. Разработка программного обеспечения by Титус Винтерс, Том Маншрек, Хайрам Райт
- Software Development Pearls. Lessons from Fifty Years of Software Experience by Karl Wiegers - 336 pages
- Lean Software Systems Engineering for Developers. Managing Requirements, Complexity, Teams, and Change Like a Champ by Doug Durham, Chad Michel - 197 pages
- Software Requirements Essentials. Core Practices for Successful Business Analysis by Karl Wiegers and Candase Hokanson - 208 pages
- Managing Software Requirements the Agile Way by Fred Heath - 214 pages
- Category:Software development books
- List of software development philosophies
- Category:Software project management
- Category:Software development philosophies
- Planning poker
- Категория:Технологии организации программирования
- Категория:Экстремальное программирование
- Экстремальное программирование
- Freeze (software engineering)
- Template:Software development process
- Software metric
- Software package metrics
- Category:Formal methods are mathematical approaches to software and hardware computer-based system development
- N-version programming is a method or process in software engineering where multiple functionally equivalent programs are independently generated from the same initial specifications.
- Artifact (software development) is one of many kinds of tangible by-products produced during the development of software.
- No Silver Bullet
-
Programming in the large and programming in the small designing a larger system as a composition of smaller parts
- A language that was designed to explicitly support programming in the large is BPEL.
- Category:Software engineering folklore
- Phabricator is a suite of web-based development collaboration tools, which includes Differential code review tool, Diffusion repository browser, Herald change monitoring tool, Maniphest bug tracker, Phriction wiki.
- Category:Software development philosophies
- Software prototyping is the activity of creating prototypes of software applications, i.e., incomplete versions of the software program being developed.
- Самая простая методология
-
The ultimate software development methodology by Zed A. Shaw
- Programming (just run this in a while loop until it's done)
- Write out a list to do
- Do some
- Test if that any good, and if not then go fix it
- Вольный перевод статьи
- Programming (just run this in a while loop until it's done)
- Programming
-
The ultimate software development methodology by Zed A. Shaw
- Wikipedia
-
Agile software development practices include
- requirements discovery and solutions improvement through the collaborative effort of self-organizing and cross-functional teams with their customer(s)/end user(s),
- adaptive planning,
- evolutionary development,
- early delivery,
- continual improvement,
- and flexible responses to changes in
- requirements,
- capacity,
- and understanding of the problems to be solved.
- Category:Agile software development
-
Agile software development practices include
- The Art of Agile Development by James Shore
- Agile Management for Software Engineering. Applying the Theory of Constraints for Business Results by David J. Anderson - 352 pages
- Pluralsight / Refine User Stories and Acceptance Criteria with Agile
- Hatjitsu :: Online Scrum Planning Poker for Agile Projects
- MountainGoatSoftware.com / Cross-Functional Collaboration in Agile: What It Does and Doesn't Mean
- “Cross functional teams are a stupid idea – no one can do everything “ by Willem-Jan Ageling
- r/agile / Does everyone has to know about everything?
- Project Management Stack Exchange / scrum - Does running an agile squad mean that all squad members can do any work, or work should be divided based on skill set?
- Wikipedia
-
Extreme programming beneficial elements of traditional software engineering practices are taken to "extreme" levels
- intended to improve software quality and responsiveness to changing customer requirements
- advocates frequent releases in short development cycles, intended to improve productivity and introduce checkpoints at which new customer requirements can be adopted
- programming in pairs (code can be reviewed continuously) or doing extensive code review
- unit testing of all code
- not programming features until they are actually needed (YAGNI)
- flat management structure
- code simplicity and clarity
- expecting changes in the customer's requirements as time passes and the problem is better understood
- frequent communication with the customer and among programmers
-
Extreme programming beneficial elements of traditional software engineering practices are taken to "extreme" levels
- wiki.c2.com/?SystemMetaphor
- DOU / Метафора системы: как повысить качество кода
- Increment is a magazine about how teams build and operate software systems at scale.
- Theoretical Computer Science Stack Exchange
- Software Engineering Stack Exchange
- LinkedIn / GitHub / As a developer, if you wanted to impress me, you should _____________.
- charlax/professional-programming A collection of learning resources for curious software engineers