Creative Commons Attribution-Share Alike 4.0 International License

Infographic: The 3 Dimensions & 3 Characteristics (3Cs) of DesOps
Creative Commons Attribution-Share Alike 4.0 International License
Download the PDF version here: https://www.slideshare.net/MobileWish/infographic-the-vicious-circle-in-teams-desops
Read related article here: https://www.linkedin.com/pulse/desops-next-wave-design-part-12-teams-vicious-circle-avoiding-dash/
©2018,”Infographic: The Vicious Circle in Teams” by Samir Dash.
Creative Commons Attribution-Share Alike 4.0 International License
©2018,”The Full-stack Roles in DesOps” by Samir Dash.
Creative Commons Attribution-Share Alike 4.0 International License.
Download PDF from https://www.slideshare.net/MobileWish/infographic-the-fullstack-roles-in-desops-desopsio
Typically the phrase “full-stack” (or full-stack developer) refers to someone who is someone comfortable and could single-handedly tackle every layer of software development. Typically DevOps engineers and full-stack developers share the same philosophical traits — they strive for greater agility and flexibility and hint at a trend towards greater generalization in the skillset of technical professionals. In case of the full-stack designer, he grows into a cross-disciplinary professional who can handle across Interaction Design, Visual Design as well as UI Development or prototyping. This helps to reduce the gaps between the outputs from these different and the effort that goes into the translation of concept flowing from one stage to another, where there are many roles assigned to more than one persons are involved (And remember that one of the key principles of DesOps is to remove waste by applying practices like Lean models).
Download the PDF version here: https://www.slideshare.net/MobileWish/the-ten-practices-of-desops-aka-designops
©2018,”The Ten Commandments of DesOps” by Samir Dash.
Creative Commons Attribution-Share Alike 4.0 International License
Download the PDF version here: https://www.slideshare.net/MobileWish/the-ten-commandments-of-desops
©2018,”The Ten Commandments of DesOps” by Samir Dash.
Creative Commons Attribution-Share Alike 4.0 International License
This “When/If – Then” tool helps to formalize hypothesis or assumption for any Hypothesis -Driven Design or Development.
This tool is helpful than the traditional elaborative templates to capture assumptions, as it was straightforward and can be used with a minimal explanation to a cross-functional crowd, a large portion of such population may not be accustomed towards the use the typical Tools and methodologies. The “When/If – Then” Tool is synonymous with the typical cause-and-effect kind of flow that is understood by and large and required very minimal explanation, and can be like any other UCD tools, can be constructed using simple post-its or printed formats.
Feel free to download and use.
Licence:
(c) 2018, “When/If – Then” Tool by Samir Dash