Software Architecture and Agility would be the topic for today Colombo Agile Meetup. Scheduled to start at 6 PM at the DHPL Building.
More Info here.
Dilan will now take questions regarding his presentation/topic.
Look outside the Agile playbook. Solutions are not going to be technical, always. – Dilan
Look to address the specifics of your problem scenario. – Dilan
Most critical challenges are driven by financials. – Dilan
Fixed bills and agile can be done together, but it is trickier. – Dilan
Software architecture is all about balance. provide maintainability, configuration and being all things to all people. – Dilan
Architect as a Manager: you might have to do a few interviews and filling in for someone else. – Dilan
Find the right way of saying no to your customer. – Dilan
Architect as a diplomat: so that you can respond to mid sprint request by customers. – Dilan
Make your code more readable so the documentation is reduced. – Dilan
Find the right techniques so that you dont need to start from scratch. – Dilan
Finding the right amount of details for you and your team could be helpful or else it will haunt you. – Dilan
The architect as a communicator: explaining the vision to the entire team. – Dilan
Knowledge sharing never gets old as long as agile and software is concerned. – Dilan
At a personal level,don’t held yourself back. look for teachable moments. – Dilan
Knowledge is more transferable in software. – Dilan
To run agile projects typically calls for greater maturity and capability. – Dilan
Architect as a mentor/teacher: they could help the teams with less experience and skill. – Dilan
It is all about asking your customers the right questions. The more you can ask, the more they can become one with you. – Dilan
The more your customer understands agile, the better the chances of them becoming a team with you. – Dilan
You should get your customer on-board with you.
Software architect as a technologist would be aware of the risks. Such as a your framework and tech getting outdated. – Dilan
Continuous Integration is your friends. – Dilan
Work with the team and the customer to come over the pre-empt issue. think ahead of the game. – Dilan
Your clients could be code-savvy, so keep them updated about the cost and progress. always. – Dilan
Technical debt is hard to convince your bosses to get it paid for you.
A negotiator should value individuals and interactions over processes and tools. – Dilan
An Architect as a Negotiator needs to know which technical debts needs to be paid off. – Dilan
See whether if the implementation is necessary and then face it out. Use opportunities to validate priority of stories. – Dilan
Always show the costs and benefits earlier as possible tan being very late. Convince your customer. – Dilan
Architect as a Negotiator is to identify which epic stories to implement. This can be hard to justify business value, but still it is necessary. – Dilan
If it is hard to justify it to yourself, just undo it. – Dilan
Implementing a solutions across the layers, is a trick you could use to validate your architecture. – Dilan
Architecture as a guide is to counterbalance the intentional architecture. – Dilan
Architect as a Guide: you put together a team and solutions should come out of the team. – Dilan
Rather than talking about Software Architect and Agility only, i’d like to take todays session in another way. – Dilan
it gives you varying levels of experience. Software architect is that lucky person who gets to balance these constrains.
Multiple positions are a bonus. – Dilan
Does agile work with offshore outsourcing?
it is used for billing models and communications over head. Cultural shock there too. – Dilan
Dilan – CTO of e-innovative is the speaker today.
Hola. This is team digit live from DHPL building 3rd floor auditorium, for Agile Meetup.