agiledesign.org
Adaptive products | Agile Design = Adaptive Design
https://agiledesign.org/category/adaptive-products-2
Agile Design = Adaptive Design. Non multa sed multum. Category Archives: Adaptive products. Limits of inspected-in quality. Posted by Valentin Tudor Mocanu. On April 4, 2016. All necessary test cases, starting from requirements. Quality has two major sources : built-in quality. Build without defects) and inspected-in quality. Test, find defects and fix them). Is – statistically speaking – a known and common problem. Traditional voice) We will test and fix, right? Traditional) That should be great! That i...
agiledesign.org
Architecture | Agile Design = Adaptive Design
https://agiledesign.org/tag/architecture
Agile Design = Adaptive Design. Non multa sed multum. Software architecture – searching for a better definition. Posted by Valentin Tudor Mocanu. On June 28, 2015. Software architecture land of confusion. Architecture it is still. A big elephant in the room. For software engineering in general and agile in particular. We do not want to make supplementary mistakes because of unappropriated definition or understanding. Focus on paper architecture instead of proven architecture by working software. Strange,...
agiledesign.org
A product it is … not a product. | Agile Design = Adaptive Design
https://agiledesign.org/2014/12/08/a-product-it-is-not-a-product
Agile Design = Adaptive Design. Non multa sed multum. A product it is … not a product. Posted by Valentin Tudor Mocanu. On December 8, 2014. What does MVP really mean…? MVP – Minimal Viable Product). That is a very interesting question. A first idea is to thing to the customer business needs: what are the minimal set of features that are needed and have relevance to be deployed first. In fact, with this first delivery, we are initiating an ecosystem, where. And other possible attributes. It is not a prod...
agiledesign.org
New product and Minimum Viable Process with DAD | Agile Design = Adaptive Design
https://agiledesign.org/2015/08/04/new-product-and-minimum-viable-process-with-dad
Agile Design = Adaptive Design. Non multa sed multum. New product and Minimum Viable Process with DAD. Posted by Valentin Tudor Mocanu. On August 4, 2015. With a new product we initiate and we must keep alive a full ecosystem. See previous post A product is not a product. 8220;) that involve:. A viable process economics. An evolving consumable solution and others. And complementary practices such. Could be a right solution to initiate such ecosystem. Use a normal project life cycle. We cannot re-use the ...
agiledesign.org
Valentin Tudor Mocanu | Agile Design = Adaptive Design
https://agiledesign.org/author/valentintudor
Agile Design = Adaptive Design. Non multa sed multum. Refactoring: strategy and collaborative work. Posted by Valentin Tudor Mocanu. On September 14, 2016. 8211; The extended definition of Refactoring contains also this part:. Note: this imaginary dialog it’s inspired from an intensive and extensive practice. What if we will have to perform a Big Refactoring? Refactoring cannot be big, it is a special kind of redesign, performed in small steps. See the above definition again. You need a strategy? Refacto...
agiledesign.org
Practices | Agile Design = Adaptive Design
https://agiledesign.org/category/practices
Agile Design = Adaptive Design. Non multa sed multum. Refactoring: strategy and collaborative work. Posted by Valentin Tudor Mocanu. On September 14, 2016. 8211; The extended definition of Refactoring contains also this part:. Note: this imaginary dialog it’s inspired from an intensive and extensive practice. What if we will have to perform a Big Refactoring? Refactoring cannot be big, it is a special kind of redesign, performed in small steps. See the above definition again. You need a strategy? Refacto...
agiledesign.org
Reactive & Adaptive Products: built-in feedback | Agile Design = Adaptive Design
https://agiledesign.org/2014/10/15/agile-reactive-adaptive-products
Agile Design = Adaptive Design. Non multa sed multum. Reactive and Adaptive Products: built-in feedback. Posted by Valentin Tudor Mocanu. On October 15, 2014. The Reactive Manifesto, initiated by Jonas Bonér, want to respond to the new context with “. With multicore and cloud computing architectures […]. With tighter SLAs in terms of lower latency, higher throughput, availability and close to linear scalability”. The event-driven nature enables the following qualities. Requirements to be reactive. How co...
agiledesign.org
Before DevOps: Delivering more by delivering less | Agile Design = Adaptive Design
https://agiledesign.org/2015/03/19/before-devops-delivering-more-by-delivering-less
Agile Design = Adaptive Design. Non multa sed multum. Before DevOps: Delivering more by delivering less. Posted by Valentin Tudor Mocanu. On March 19, 2015. Undesired complexity give undesired deliveries. There are many aspects to consider related to DevOps and delivery, many strategies and (in the right context and the right approach) there are also some very useful tools. It is a complex issue and. Last thing that we want is to make that even harder because of undesired complexity. If the business rule.
agiledesign.org
Just in time and Envisioning versus complexity | Agile Design = Adaptive Design
https://agiledesign.org/2015/05/26/just-in-time-and-envisioning-versus-complexity
Agile Design = Adaptive Design. Non multa sed multum. Just in time and Envisioning versus complexity. Posted by Valentin Tudor Mocanu. On May 26, 2015. Principles for reducing complexity:. Apply envisioning for accessible information and just-in-time for what is far from certainty. That is matching with the logic of Stacey Matrix. Just-in-time is not (always) a silver bullet. We need process approaches that effectively cover both dimensions #agilemodeling #DAD. Larr; DRY principle beyond small talks.
agiledesign.org
Home | Agile Design = Adaptive Design
https://agiledesign.org/category/home
Agile Design = Adaptive Design. Non multa sed multum. Limits of inspected-in quality. Posted by Valentin Tudor Mocanu. On April 4, 2016. All necessary test cases, starting from requirements. Quality has two major sources : built-in quality. Build without defects) and inspected-in quality. Test, find defects and fix them). Is – statistically speaking – a known and common problem. Traditional voice) We will test and fix, right? Traditional) That should be great! That is true, but there are difference: TDD ...
SOCIAL ENGAGEMENT