aspose file tools*
The moose likes Design and the fly likes Software architecture details: What are the technical risks involved? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Design
Bookmark "Software architecture details: What are the technical risks involved?" Watch "Software architecture details: What are the technical risks involved?" New topic
Author

Software architecture details: What are the technical risks involved?

charlsy chuks
Ranch Hand

Joined: May 18, 2012
Posts: 79
Hi Simon,
In the book, you posed some interesting questions. I hope this won't be regarded as cheating but here are my questions that
spin off from the main question: What are the technical risks involved?

What is a risk? Are all risks equal?
Who identifies the technical risks in your team?
Who looks after the technical risks in your team? If it’s the (typically non-technical) project manager or ScrumMaster, is this a good idea?
What happens if you ignore technical risks?
How can you pro-actively deal with technical risks?

Thanks
Simon Brown
sharp shooter, and author
Ranch Hand

Joined: May 10, 2000
Posts: 1913
    
    6
haha, cheating, those questions sound familiar ... https://leanpub.com/software-architecture-for-developers/read#questions-6

As I've said in some of the other threads, I basically take a risk-driven approach to architecture in order to stack the odds of a successful delivery in my favour. Too much risk-mitigation quickly leads back to big design up front and analysis paralysis though.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Software architecture details: What are the technical risks involved?