Commits

Herbert Breunung committed 678b853

planning phase of CP

  • Participants
  • Parent commits 8256cb5
  • Branches sp3

Comments (0)

Files changed (1)

File doc/CompleteProgramming.pod

        and accumulates additional work as the project grows.
        It should be possible to combine sound planning, practicability and quick results.
 
-    2) Writing tests is no silver bullet and is used for several competing purposes.
+    2) The awesome powers of prototypes are still not fully used.
 
-    3) The awesome powers of prototypes are still not fully used.
+    3) Documentation coverage and depth matters a great deal and writing it
+       would also help the developer.
 
-    4) All methodologies I know of overlook several aspects of the product.
+    4) Writing tests is no silver bullet and is used for several competing purposes.
+
+    5) All methodologies I know of overlook several aspects of the product.
        That includes even "documentation driven development",
        which gave important impulses for the creation of CP.
 
-    5) New tools like hg or git allow new workflows which solve pending problems.
+    6) New tools like hg or git allow new workflows which solve pending problems.
 
 
 =head3 Main Goal
 
 =head3 Planning
 
-aprox. feature set
-what kind of team to solve it with
-resources
+First step: should be writing down the approximate feature set, save and commit it.
+Its now part of the documentation and also serves as the todo.
 
-what technologies, languages, libs, os, other tools
-fallback alternatives or areas you might expand into
+Second step: think what what technologies, languages, libs, os, other tools
+you should select and procede as in step one.
+Spend some minutes on fallback alternatives or areas you might expand into.
+Also consider now what kind of team could solve that task.
+
+Rough drafts are all you need.
 
 
 =head3 Prototypes